Re: xlog.c: removing ReadRecPtr and EndRecPtr - Mailing list pgsql-hackers

From Robert Haas
Subject Re: xlog.c: removing ReadRecPtr and EndRecPtr
Date
Msg-id CA+TgmobX5GVTYU20nQzuudemg1KFmbXANEURHyxQRiEVrEVQ1Q@mail.gmail.com
Whole thread Raw
In response to Re: xlog.c: removing ReadRecPtr and EndRecPtr  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: xlog.c: removing ReadRecPtr and EndRecPtr
List pgsql-hackers
On Thu, Nov 18, 2021 at 2:21 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Would it work to start postmaster directly instad of using pg_ctl, and
> then rely on (say) pg_isready?

I *think* that pg_isready would also fail, because the documentation
says "pg_isready returns 0 to the shell if the server is accepting
connections normally, 1 if the server is rejecting connections (for
example during startup) ..." and I believe the "during startup" case
would apply here.

Starting postmaster directly is a thought. Is there any existing
precedent for that approach?

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: xlog.c: removing ReadRecPtr and EndRecPtr
Next
From: Tom Lane
Date:
Subject: Re: xlog.c: removing ReadRecPtr and EndRecPtr