Re: walsender.c comment with no context is hard to understand - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: walsender.c comment with no context is hard to understand
Date
Msg-id CAA4eK1KDh+2BwtxCFs_Epkn9ueSD8G+hErJryW+e8v3AELcgWA@mail.gmail.com
Whole thread Raw
In response to Re: walsender.c comment with no context is hard to understand  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: walsender.c comment with no context is hard to understand
List pgsql-hackers
On Mon, Jul 8, 2024 at 11:08 AM Bertrand Drouvot
<bertranddrouvot.pg@gmail.com> wrote:
>
> On Mon, Jul 08, 2024 at 08:46:19AM +0530, Amit Kapila wrote:
> > This sounds better but it is better to add just before we determine
> > am_cascading_walsender as is done in the attached. What do you think?
>
> Thanks! LGTM.
>

I would like to push this to HEAD only as we don't see any bug that
this change can prevent. What do you think?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: replace strtok()
Next
From: jian he
Date:
Subject: Re: SupportRequestRows support function for generate_series_timestamptz