Re: Failure with 004_logrotate in prairiedog - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Failure with 004_logrotate in prairiedog
Date
Msg-id 234876.1626704626@sss.pgh.pa.us
Whole thread Raw
In response to Re: Failure with 004_logrotate in prairiedog  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Failure with 004_logrotate in prairiedog  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Jul 19, 2021 at 04:15:36PM +0900, Kyotaro Horiguchi wrote:
>> When rotation happens, the metainfo file is once removed then
>> created. If slurp_file in the metafile-checking loop hits the gap, the
>> slurp_file fails with ENOENT.

> I can read the following code, as of update_metainfo_datafile():
> if (rename(LOG_METAINFO_DATAFILE_TMP, LOG_METAINFO_DATAFILE) != 0)

Yeah, ignore my previous message.  There is an unlink up at the top
of the function, which fooled me in my caffeine-deprived state.
But that path is only taken when logging was just turned off, so
we must remove the now-irrelevant metafile.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Failure with 004_logrotate in prairiedog
Next
From: John Naylor
Date:
Subject: Re: postgresql.conf.sample missing units