| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 9.2.3 crashes during archive recovery |
| Date: | 2013-02-13 20:15:03 |
| Message-ID: | 511BF447.7040200@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13.02.2013 17:02, Tom Lane wrote:
> Heikki Linnakangas<hlinnakangas(at)vmware(dot)com> writes:
>> At least in back-branches, I'd call this a pilot error. You can't turn a
>> master into a standby just by creating a recovery.conf file. At least
>> not if the master was not shut down cleanly first.
>> ...
>> I'm not sure that's worth the trouble, though. Perhaps it would be
>> better to just throw an error if the control file state is
>> DB_IN_PRODUCTION and a recovery.conf file exists.
>
> +1 for that approach, at least until it's clear there's a market for
> doing this sort of thing. I think the error check could be
> back-patched, too.
Hmm, I just realized a little problem with that approach. If you take a
base backup using an atomic filesystem backup from a running server, and
start archive recovery from that, that's essentially the same thing as
Kyotaro's test case.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-02-13 20:17:27 | Re: Alias hstore's ? to ~ so that it works with JDBC |
| Previous Message | Pavel Stehule | 2013-02-13 20:07:54 | proposal or just idea for psql - show first N rows from relation backslash statement |