From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | alvherre(at)alvh(dot)no-ip(dot)org, michael(at)paquier(dot)xyz, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inconvenience of pg_read_binary_file() |
Date: | 2022-08-01 08:41:48 |
Message-ID: | 20220801.174148.1664369784655078240.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Sat, 30 Jul 2022 10:24:39 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > On 2022-Jul-30, Michael Paquier wrote:
> >> PG_VERSION would be simpler. Looking at postmaster.pid would require
> >> a lookup at external_pid_file, and as it is not set by default you
> >> would need to add some extra logic in the tests where
> >> external_pid_file = NULL <=> PGDATA/postmaster.pid.
>
> > Hmm, no? as I recall external_pid_file is an *additional* PID file; it
> > doesn't supplant postmaster.pid.
>
> Right. postmaster.pid absolutely should be there if the postmaster
> is up (and if it ain't, you're going to have lots of other difficulty
> in running the regression tests...). It doesn't feel quite as static
> as PG_VERSION, though.
Thanks for committing it. Also the revised test (being suggested by
Michael) looks good.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-08-01 08:51:56 | Re: Handle infinite recursion in logical replication setup |
Previous Message | Peter Smith | 2022-08-01 08:02:21 | Re: Handle infinite recursion in logical replication setup |