| 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 22:32:01 |
| Message-ID: | 167106.1626647521@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:
> On Sun, Jul 18, 2021 at 01:42:18AM -0400, Tom Lane wrote:
>> 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.
> Thanks for the pointer. This indeed looks like the same problem.
For context, dromedary (now florican) is a dual-CPU machine while
prairiedog has but one CPU. I'd thought that maybe not being
multi-CPU insulated prairiedog from the non-atomic-rename problem.
But now it looks like it's merely a lot less probable on that hardware.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2021-07-18 23:42:37 | Re: [PATCH] Allow multiple recursive self-references |
| Previous Message | Michael Paquier | 2021-07-18 22:06:15 | Re: Failure with 004_logrotate in prairiedog |