pg.ddx.io  pgdogdev/pgdog GitHub issues and pull requests  
help / color / mirror / Atom feed
From: levkk (@levkk) <noreply+levkk@github.com>
To: pgdogdev/pgdog <noreply+pgdogdev-pgdog@github.com>
Subject: Re: [pgdogdev/pgdog] PR #2058: feat(resharding): add initial setup for resumable resharding tasks
Date: Wed, 18 Nov 2026 18:28:04 +0000
Message-ID: <gh-pgdogdev-pgdog-2058-rc4618885484@github.com> (raw)
In-Reply-To: <gh-pgdogdev-pgdog-2058@github.com>
References: <gh-pgdogdev-pgdog-2058@github.com>

(on pgdog/src/backend/replication/logical/run/watchdog.rs:24)

It's not clear why you need this. Presumably, the same connection is holding the advisory lock as the one used for replication & copying data. Otherwise, the `pgdog.resharding` data is not written atomically as desired?

If that's the case, you don't need to check its health. You can just assume the advisory lock is held throughout for as long as the connection is alive and accepting copy data or replication commands.

view thread (38+ messages)  latest in thread

Message-ID: <gh-pgdogdev-pgdog-2058-rc4618885484@github.com>
Permalink:  ../gh-pgdogdev-pgdog-2058-rc4618885484@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox