Re: Is Recovery actually paused?
От | Dilip Kumar |
---|---|
Тема | Re: Is Recovery actually paused? |
Дата | |
Msg-id | CAFiTN-vwNKammUbs9TGQxv8t6ZXNGnQVg9Z-0GDzhF=O_yX9RA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Is Recovery actually paused? (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: Is Recovery actually paused?
|
Список | pgsql-hackers |
On Wed, Jan 27, 2021 at 12:50 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Tue, Jan 26, 2021 at 2:00 AM Robert Haas <robertmhaas@gmail.com> wrote: > > > > On Sat, Jan 23, 2021 at 6:10 AM Bharath Rupireddy > > <bharath.rupireddyforpostgres@gmail.com> wrote: > > > +1 to just show the recovery pause state in the output of > > > pg_is_wal_replay_paused. But, should the function name > > > "pg_is_wal_replay_paused" be something like > > > "pg_get_wal_replay_pause_state" or some other? To me, when "is" exists > > > in a function, I expect a boolean output. Others may have better > > > thoughts. > > > > Maybe we should leave the existing function pg_is_wal_replay_paused() > > alone and add a new one with the name you suggest that returns text. > > That would create less burden for tool authors. > > +1 > Yeah, we can do that, I will send an updated patch soon. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: