Re: Failure with 004_logrotate in prairiedog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Failure with 004_logrotate in prairiedog
Date: 2021-07-18 05:42:18
Message-ID: 109974.1626586938@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> prairiedog has failed in a way that seems a bit obscure to me:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prairiedog&dt=2021-07-18%2000%3A23%3A29
> ...
> We could use some eval blocks in this area, but a non-atomic rename()
> would cause problems in more areas. Thoughts?

Awhile back we discovered that old macOS versions have non-atomic rename
[1]. I eventually shut down dromedary because that was causing failures
often enough to be annoying. I'd not seen such a failure before on
prairiedog, but it sure seems plausible that this is one.

regards, tom lane

[1] https://www.postgresql.org/message-id/2636.1569016167@sss.pgh.pa.us

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2021-07-18 10:17:55 Re: CREATE COLLATION - check for duplicate options and error out if found one
Previous Message Michael Paquier 2021-07-18 03:37:48 Re: Added documentation for cascade and restrict option of drop statistics