Re: when the startup process doesn't - Mailing list pgsql-hackers

From Tom Lane
Subject Re: when the startup process doesn't
Date
Msg-id 633337.1618945018@sss.pgh.pa.us
Whole thread Raw
In response to Re: when the startup process doesn't  (Stephen Frost <sfrost@snowman.net>)
Responses Re: when the startup process doesn't  (Stephen Frost <sfrost@snowman.net>)
Re: when the startup process doesn't  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> Yeah, being able to pick up on this remotely seems like it'd be quite
> nice.  I'm not really thrilled with the idea, but the best I've got
> offhand for this would be a new role that's "pg_recovery_login" where an
> admin can GRANT that role to the roles they'd like to be able to use to
> login during the recovery process and then, for those roles, we write
> out flat files to allow authentication without access to pg_authid,

We got rid of those flat files for good and sufficient reasons.  I really
really don't want to go back to having such.

I wonder though whether we really need authentication here.  pg_ping
already exposes whether the database is up, to anyone who can reach the
postmaster port at all.  Would it be so horrible if the "can't accept
connections" error message included a detail about "recovery is X%
done"?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: when the startup process doesn't
Next
From: Stephen Frost
Date:
Subject: Re: PATCH: Add GSSAPI ccache_name option to libpq