From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "pg_ctl: the PID file ... is empty" at end of make check |
Date: | 2019-10-15 01:39:16 |
Message-ID: | CA+hUKG+h-tWhpogqA93xh0zuTchbJ-9ZtV0X=-j-=vW8n1DPRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 15, 2019 at 1:55 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> > Agreed. Secret non-shareable bug report filed. Fingers crossed.
>
> Since that conversation, longfin has shown the same symptom
> just once more:
>
> longfin | REL_11_STABLE | 2019-07-28 22:29:03 | recoveryCheck | waiting for ser
> ver to shut down......pg_ctl: the PID file "/Users/buildfarm/bf-data/REL_11_STAB
> LE/pgsql.build/src/test/recovery/tmp_check/t_001_stream_rep_standby_2_data/pgdat
> a/postmaster.pid" is empty
>
> and now prairiedog has shown it too:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prairiedog&dt=2019-10-14%2021%3A45%3A47
>
> which is positively fascinating, because prairiedog is running a
> bronze-age version of macOS that surely never heard of APFS.
> So this makes it look like this is a basic macOS bug that's not
> as filesystem-dependent as one might think.
Does https://github.com/macdice/unlinktest show the problem on that system?
> Trawling the buildfarm database finds no other matches in the last year,
> so whatever it is, it's pretty darn improbable.
>
> Did you ever get any reaction to that bug report?
No acknowledgement. I did learn from an anonymous source that "it’s
prioritized and in the queue".
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2019-10-15 03:53:48 | ProcArrayGroupClearXid() compare-exchange style |
Previous Message | Tom Lane | 2019-10-15 00:54:55 | Re: "pg_ctl: the PID file ... is empty" at end of make check |