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

From Bertrand Drouvot
Subject Re: walsender.c comment with no context is hard to understand
Date
Msg-id Zot7UVF+gY71dDoQ@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: walsender.c comment with no context is hard to understand  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: walsender.c comment with no context is hard to understand
List pgsql-hackers
Hi,

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.

> 
> BTW, is it possible that the promotion gets completed after we wait
> for the required WAL and before assigning am_cascading_walsender?

Yeah, I don't think there is anything that would prevent a promotion to
happen and complete here. I did a few tests (pausing the walsender with gdb at
various places and promoting the standby).

> think even if that happens we can correctly determine the required
> timeline because all the required WAL is already available, is that
> correct 

Yeah that's correct.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Pluggable cumulative statistics
Next
From: David Steele
Date:
Subject: Re: replace strtok()