Re: pgsql: Prevent invalidation of newly synced replication slots.
| От | Robert Haas |
|---|---|
| Тема | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| Дата | |
| Msg-id | CA+TgmoZZtHcY200WKPSfOdAhNfjC_NTuRSkdr0jkQXC2zdRcAQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pgsql: Prevent invalidation of newly synced replication slots. (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: pgsql: Prevent invalidation of newly synced replication slots.
|
| Список | pgsql-hackers |
On Wed, Jan 28, 2026 at 7:35 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > Does this fix/theory sound plausible? I wondered about this yesterday, too. I didn't actually understand how the existence of the background psql could be causing the failure, but I thought it might be. However, I couldn't figure out the correct incantation to get rid of it in my testing, as I thought I would need to detach the injection point first or something. If it fixes it for you, I would suggest committing promptly. I think we are too dependent on CI now to leave it broken for any period of time, and indeed I suggest getting set up so that you test your commits against it before committing. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: