| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alena Vinter <dlaaren8(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Ilyasov Ian <ianilyasov(at)outlook(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Resetting recovery target parameters in pg_createsubscriber |
| Date: | 2025-11-19 19:49:29 |
| Message-ID: | CA+TgmoYotQtTnNp2gjinRfdcV8qmEZcTtU1JmA9LLztebKkJSQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 13, 2025 at 7:46 AM Alena Vinter <dlaaren8(at)gmail(dot)com> wrote:
> Robert, here's a realistic scenario where the issue occurs:
> 1. Start with a primary and physical standby
> 2. Convert the standby to a logical replica using `pg_createsubscriber`
> 3. Later, create a new physical standby from a backup of this logical replica
> 4. The new standby fails to start because it cannot reach consistency point
>
> The root cause is that `pg_createsubscriber` leaves behind recovery parameters that interfere with the new standby's startup process, causing recovery to stop before reaching a consistency point.
Yes, I agree this is a much better scenario to test. Thanks.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Holmberg | 2025-11-19 19:54:58 | Re: ON CONFLICT DO SELECT (take 3) |
| Previous Message | Robert Haas | 2025-11-19 19:47:36 | Re: Non-blocking archiver process |