| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Amit Kapila <akapila(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| Date: | 2026-01-28 12:57:49 |
| Message-ID: | CA+TgmoZZtHcY200WKPSfOdAhNfjC_NTuRSkdr0jkQXC2zdRcAQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 28, 2026 at 7:35 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-01-28 14:23:30 | pgsql: Fix duplicate arbiter detection during REINDEX CONCURRENTLY on p |
| Previous Message | Amit Kapila | 2026-01-28 12:35:10 | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ahmed Et-tanany | 2026-01-28 13:02:01 | Re: [PATCH] Add max_logical_replication_slots GUC |
| Previous Message | Álvaro Herrera | 2026-01-28 12:54:32 | Re: [PATCH] Add max_logical_replication_slots GUC |