| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Add DBState to pg_control_system function |
| Date: | 2022-02-01 04:22:26 |
| Message-ID: | CALj2ACWBFEDA4a6EGn6F6ADLUqn-XieUy-wWvLdzR6R_yVknGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I think emitting DBState (staring up, shut down, shut down in
recovery, shutting down, in crash recovery, in archive recovery, in
production) via the pg_control_system function would help know the
database state, especially during PITR/archive recovery. During
archive recovery, the server can open up for read-only connections
even before the archive recovery finishes. Having, pg_control_system
emit database state would help the users/service layers know it and so
they can take some actions based on it.
Attaching a patch herewith.
Thoughts?
Regards,
Bharath Rupireddy.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-DBState-to-pg_control_system-function.patch | application/octet-stream | 6.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kuroda.hayato@fujitsu.com | 2022-02-01 04:37:07 | RE: [Proposal] Add foreign-server health checks infrastructure |
| Previous Message | Fujii Masao | 2022-02-01 04:19:43 | Re: Add checkpoint and redo LSN to LogCheckpointEnd log message |