Tag replication connections with per-worker application_name#882
Open
jmqd wants to merge 10 commits into
Open
Conversation
Apply and table sync replication connections now report
{base}:apply:{pipeline_id} and {base}:tsync:{pipeline_id}:{table_oid}
in pg_stat_activity. Child copy connections inherit the parent worker's
name. Overlong names clamp the base and keep the worker suffix intact.
Rename budget to max_allowed_len, use floor_char_boundary instead of a manual boundary loop, and trim connect_for_* doc comments.
|
coverage: 72.923% (+0.08%) from 72.841% — jm/per-worker-application-name into main |
iambriccardo
reviewed
Jul 8, 2026
The longer tag narrows the no-clamp bound to 15 combined digits of pipeline id and table oid; beyond that the base clamps and the suffix survives. Length tests restated around the new bound.
Clamping is expected with long pipeline ids and table oids, not an anomaly worth a warning.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All ETL replication connections currently report the same
application_name, so from the server's side the apply worker and every table-sync copy connection are indistinguishable.This tags each worker connection with its identity:
supabase_etl_replicator_replication:apply:{pipeline_id}supabase_etl_replicator_replication:tsync:{pipeline_id}:{table_oid}Two motivations:
pg_stat_activityandpg_terminate_backendsit. Without them, tests have to guess by PID heuristics, which flakes.pg_stat_activityandpg_stat_replicationnow show which worker (and which table) owns each connection, lock wait, and terminated backend.