From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: when the startup process doesn't |
Date: | 2021-04-19 23:16:37 |
Message-ID: | 20210419231637.GA24815@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021-Apr-19, Robert Haas wrote:
> Another possible approach would be to accept connections for
> monitoring purposes even during crash recovery. We can't allow access
> to any database at that point, since the system might not be
> consistent, but we could allow something like a replication connection
> (the non-database-associated variant).
Hmm. We already have pg_isready, which is pretty simplistic -- it tries
to connect to the server and derive a status in a very simplistic way.
Can we perhaps improve on that? I think your idea of using the
non-database-connected replication mode would let the server return a
tuple with some status information with a new command. And then
pg_isready could interpret that, or just print it.
--
Álvaro Herrera 39°49'30"S 73°17'W
Subversion to GIT: the shortest path to happiness I've ever heard of
(Alexey Klyukin)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-04-19 23:22:47 | Re: Free port choosing freezes when PostgresNode::use_tcp is used on BSD systems |
Previous Message | Tom Lane | 2021-04-19 23:10:05 | Re: "could not find pathkey item to sort" for TPC-DS queries 94-96 |