From: | Christoph Berg <christoph(dot)berg(at)credativ(dot)de> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [BUG] Archive recovery failure on 9.3+. |
Date: | 2014-02-13 13:53:41 |
Message-ID: | 20140213135341.GC25703@msgid.credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Heikki Linnakangas 2014-02-13 <52FCCA40(dot)3060908(at)vmware(dot)com>
> I was testing this with streaming replication; 9.1 and 9.2 behave
> the same in that scenario. But they differ when doing archive
> recovery.
>
> Is this an argument for back-patching the "don't archive last
> segment from old timeline" patch to 9.2 and 9.3, but leaving 9.1
> alone? You have the same problem with 9.1 and streaming replication,
> but no-one's complained..
I can't say what would be better from a technical viewpoint. For me,
this is literally an academic problem people run into when they try
replication during the PostgreSQL course, using the archive_command
example from postgresql.conf. I guess if no one else has complained
yet, there's no reason to touch the back branches.
Is removing the "test ! -f" part and hence overwriting files in the
archive safe, i.e. are the files the same?
Mit freundlichen Grüßen,
Christoph Berg
--
Senior Berater, Tel.: +49 (0)21 61 / 46 43-187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Hohenzollernstr. 133, 41061 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
pgp fingerprint: 5C48 FE61 57F4 9179 5970 87C6 4C5A 6BAB 12D2 A7AE
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-02-13 14:01:16 | Re: [BUG] Archive recovery failure on 9.3+. |
Previous Message | Magnus Hagander | 2014-02-13 13:43:40 | Re: Prevent pg_basebackup -Fp -D -? |