| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add %r substitution for psql prompts to show recovery status |
| Date: | 2017-12-07 21:26:40 |
| Message-ID: | CA+TgmoZkyE_UXn5k6eSaxyXX+2UOzkoqSmLGmF_yMb2k+CMXrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 6, 2017 at 9:19 PM, Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> wrote:
> Note this substitution sends a "pg_is_in_recovery()" query to the server
> each time it's encountered; unless there's something I'm overlooking I
> think that's the only reliable way to determine current recovery status.
That seems kinda painful.
And what happens in an aborted transaction?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-12-07 21:30:47 | Re: ERROR: too many dynamic shared memory segments |
| Previous Message | Robert Haas | 2017-12-07 21:07:09 | Re: [HACKERS] Proposal: Local indexes for partitioned table |