Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.
Date: 2025-03-13 01:05:02
Message-ID: CAD21AoBFDi3YwidD6pXvcRW=xA5CRU6SQ+DSWxhSHrQEFiQXgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 11, 2025 at 4:26 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> On Tue, Feb 11, 2025 at 9:36 PM Hayato Kuroda (Fujitsu)
> <kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> >
> > Dear Sawada-san,
> >
> > Thanks for updating the patch!
> >
> > > I've attached the updated patch. I address all comments I got so far
> > > and added a small regression test.
> > >
> > > It makes sense to me that we move GetDbnameFromConnectionOptions() to
> > > recovery_gen.c since this function is currently used only with
> > > GenerateRecoveryConfig() which is defined in the same file. If we find
> > > a more appropriate place, we can move it later. Feedback is very
> > > welcome.
> >
> > I considered your idea that adding new API, but it seemed for me to have less
> > benefit. Also, I do not know better place for the declaration now. Overall, the
> > patch looks good to me.
> >
>
> I'm going to push the v2 patch, barring any objections and further comments.

Pushed.

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-03-13 01:39:41 Re: Dubious server log messages after pg_upgrade
Previous Message Michael Paquier 2025-03-13 00:42:17 Re: PGSERVICEFILE as part of a normal connection string