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.
On 2022/02/01 13:22, Bharath Rupireddy wrote: > 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? This information seems not so helpful because only "in production" and "archive recovery" can be reported during normal runningand recovery, respectively. No? In the state other than them, we cannot connect to the server and execute pg_control_system(). Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера