Re: archive status ".ready" files may be created too early - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: archive status ".ready" files may be created too early
Date
Msg-id FFB63CF3-4F26-4A1A-ACEC-3E1172F35DE1@amazon.com
Whole thread Raw
In response to Re: archive status ".ready" files may be created too early  ("alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org>)
Responses Re: archive status ".ready" files may be created too early  ("alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On 8/18/21, 10:06 AM, "alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org> wrote:
> So that comment suggests that we should give the responsibility to bgwriter.
> This seems good enough to me.  I suppose if bgwriter has a long run of
> buffers to write it could take a little bit of time (a few hundred
> milliseconds?) but I think that should be okay.

Do you think bgwriter should be the only caller of
NotifySegmentsReadyForArchive(), or should we still have XLogWrite()
call it?

Nathan


pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: NAMEDATALEN increase because of non-latin languages
Next
From: "alvherre@alvh.no-ip.org"
Date:
Subject: Re: archive status ".ready" files may be created too early