Re: Improve pg_sync_replication_slots() to wait for primary to advance
От | Ashutosh Bapat |
---|---|
Тема | Re: Improve pg_sync_replication_slots() to wait for primary to advance |
Дата | |
Msg-id | CAExHW5tVvjD8LKoz=evPwgj11pqOYM4xDqnC4UwE-c5f-ZeWAg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Improve pg_sync_replication_slots() to wait for primary to advance (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Improve pg_sync_replication_slots() to wait for primary to advance
|
Список | pgsql-hackers |
On Sat, Sep 6, 2025 at 9:14 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Fri, Sep 5, 2025 at 11:39 PM Ashutosh Sharma <ashu.coek88@gmail.com> wrote: > > If the remote slot is inactive since long and lagging behind the > > standby, this function (pg_sync_replication_slots) could end up > > waiting indefinitely. While it can certainly be cancelled manually, > > that behavior might not be ideal for everyone. That’s my > > understanding; please let me know if you see it differently. > > > > Such a case can be addressed by having additional timeout parameters. > We can do that as an additional patch if the use case is important > enough to address. > Or we could rely on statement_timeout or the user cancelling the query explicitly. -- Best Wishes, Ashutosh Bapat
В списке pgsql-hackers по дате отправления: