| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, David Steele <david(at)pgmasters(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Standby accepts recovery_target_timeline setting? |
| Date: | 2019-10-09 11:50:33 |
| Message-ID: | CA+TgmoZY4ecVRgz+7uVBAythtyxS-MiSg3Sn6Eayt+8w2S+19g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 8, 2019 at 9:58 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> From a user
> perspective, what happens when you've started up PG as a primary, since
> you don't have a signal file in place to indicate that you're doing
> recovery, and you have a recovery_target set, so some user does
> "show recovery_target_name" and sees a value? How is that sensible?
I'd argue that not only is it sensible, but it's the only correct
answer. If I put a value in postgresql.conf and it doesn't show up in
the output of SHOW, I'm going to be confused. That just seems flat
wrong to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2019-10-09 12:07:40 | Re: v12 and pg_restore -f- |
| Previous Message | Dilip Kumar | 2019-10-09 10:12:18 | Re: maintenance_work_mem used by Vacuum |