Re: Stop the search once replication origin is found

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Stop the search once replication origin is found
Date: 2023-11-22 08:48:58
Message-ID: CAA4eK1LmUVPCNwoHcWzRhMca5PA1sBp+UrbdqmU8XfJuu6SMiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 20, 2023 at 4:36 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Mon, Nov 20, 2023 at 2:36 PM Antonin Houska <ah(at)cybertec(dot)at> wrote:
> >
> > Although it's not performance-critical, I think it just makes sense to break
> > the loop in replorigin_session_setup() as soon as we've found the origin.
> >
>
> Your proposal sounds reasonable to me.
>

Pushed, thanks for the patch!

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-11-22 08:57:58 Re: Lockless exit path for ReplicationOriginExitCleanup
Previous Message Amit Kapila 2023-11-22 08:47:40 Re: [PoC] pg_upgrade: allow to upgrade publisher node