Re: Is Recovery actually paused? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Is Recovery actually paused?
Date
Msg-id CA+TgmoYG0RKrcyCt_kbmTRFd9r05rv=ZoD59S_c-AzFLt5_N5A@mail.gmail.com
Whole thread Raw
In response to Re: Is Recovery actually paused?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Is Recovery actually paused?  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
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.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: cleaning up a few CLOG-related things
Next
From: vignesh C
Date:
Subject: Re: Identify missing publications from publisher while create/alter subscription.