Re: Inconvenience of pg_read_binary_file()

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Inconvenience of pg_read_binary_file()
Date: 2022-07-30 11:47:05
Message-ID: 20220730114705.fkj4ysedujpao6sy@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

postmaster.opts is also an option.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"E pur si muove" (Galileo Galilei)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-07-30 12:54:33 Re: [PATCH] Add extra statistics to explain for Nested Loop
Previous Message Alvaro Herrera 2022-07-30 11:39:22 Re: making relfilenodes 56 bits