Re: Replication slot is not able to sync up
От | Amit Kapila |
---|---|
Тема | Re: Replication slot is not able to sync up |
Дата | |
Msg-id | CAA4eK1JKXCMDqfFgNtemVZ9ge4KrQtwSQG1OwMLNHRBDfnH9rA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Replication slot is not able to sync up (shveta malik <shveta.malik@gmail.com>) |
Список | pgsql-hackers |
On Thu, May 29, 2025 at 8:39 AM shveta malik <shveta.malik@gmail.com> wrote: > > On Wed, May 28, 2025 at 11:56 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > > > > > I didn't know it was intended for testing and debugging purposes so > > clearilying it in the documentation would be a good idea. > > I have added the suggested docs in v3. > - errmsg("could not synchronize replication slot \"%s\"", remote_slot->name), - errdetail("Logical decoding could not find consistent point from local slot's LSN %X/%X.", + errmsg("could not synchronize replication slot \"%s\" to prevent data loss", remote_slot->name), + errdetail("Standby does not have enough data to decode WALs at LSN %X/%X.", LSN_FORMAT_ARGS(slot->data.restart_lsn))); I find the errdetail is not clear about the current state, which is that we can't yet build a consistent snapshot on the standby to allow decoding. Would it be better to have errdetail like: "Standby could not build a consistent snapshot to decode WALs at LSN %X/%X.? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: