From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Warn about using single user + standby_mode |
Date: | 2015-06-06 03:05:57 |
Message-ID: | CAA4eK1L5mGnyrV8r0KytorpsjeiREbdhQo=9Se3kXoeCQXjSEg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 5, 2015 at 9:59 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> Hi,
>
> When primary_conninfo is configured and standby_mode is enabled single
> user mode starts up, but at some point will just wait in a latch for WAL
> to show up. Which will obviously never happen as walreceiver isn't up.
>
So this essentially means as it stands single user mode can't work
for standby.
> Should we just error out in that case, or at least display a log message
> about that fact?
>
I think error is better in this case as there seems no chance for
user to proceed in this case. It is even better if we can detect
this early and error out before even reaching the stage where it
starts waiting out for WAL to show up.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-06-06 03:07:08 | Re: [CORE] Restore-reliability mode |
Previous Message | Alvaro Herrera | 2015-06-06 01:25:55 | Re: could not truncate directory "pg_subtrans": apparent wraparound |