Re: Resetting recovery target parameters in pg_createsubscriber

From: Alena Vinter <dlaaren8(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Resetting recovery target parameters in pg_createsubscriber
Date: 2025-09-30 05:22:08
Message-ID: CAGWv16+4nScya9TX_Ctx96B+kouwpqF+M2LmotK97ThiHMypMQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

HI Michael,

Thank you for the review!

> Why not just
> switch recovery_params_set to false once ReplaceRecoveryConfig() is
> called?

Stupid me!

> Why do we need to call again GenerateRecoveryConfig() when resetting
> recovery.conf/postgresql.conf.sample with its original contents before
> switching the system ID of the new replica? I may be missing
> something, of course, but we're done with recovery so I don't quite
> see the point in appending the recovery config generated with the
> original contents. If this is justified (don't think it is), this
> deserves a comment to explain the reason behind this logic.

This relates to the point I mentioned earlier about being unsure whether we
should preserve `primary_conninfo`:
> I kept primary_conninfo as-is for now since I'm not totally sure if we
need to touch it

The reason I called `GenerateRecoveryConfig()` was to regenerate the
`primary_conninfo` string in the recovery configuration file. If we should
remove it, then the reset function can be much simpler. Could you please
help me to clarify should we regenerate `primary_conninfo` or we can safely
purge it?

Best regards,
Alena Vinter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-09-30 05:24:49 Re: Fixing MSVC's inability to detect elog(ERROR) does not return
Previous Message Nitin Motiani 2025-09-30 05:16:11 Re: pgstattuple "unexpected zero page" for gist and hash indexes