From: | Christoph Berg <cb(at)df7cb(dot)de> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, bohmer(at)visionlink(dot)org, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Re: BUG #8043: 9.2.4 doesn't open WAL files from archive, only looks in pg_xlog |
Date: | 2013-04-09 11:59:25 |
Message-ID: | 20130409115925.GC26705@msgid.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Re: Jeff Janes 2013-04-06 <CAMkU=1zvioQvMgbWssHv3DnXMNeEJmqtq_5hJqLGx8i4eGAQJg(at)mail(dot)gmail(dot)com>
> I don't think the docs are very clear on that. They say "This file will of
> course be archived as a part of your backup dump file", but "will be" does
> not imply "must be". Elsewhere it emphasizes that the label you gave to
> pg_start_backup is written into the file, but doesn't really say what the
> file itself is there for. To me it seems to imply that the file is there
> for your convenience, to hold that label, and not as a critical part of the
> system.
This was also my impression, tbh :-/. And the problem just popped up
again independently on #postgresql.
> Patch attached, which I hope can be back-patched. I'll also add it to
> commitfest-Next.
+1. It makes the documentation clearer on this.
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
From | Date | Subject | |
---|---|---|---|
Next Message | th | 2013-04-09 15:01:33 | BUG #8049: Incorrect results when using ORDER BY and query planner options |
Previous Message | luigisag | 2013-04-09 09:47:17 | BUG #8048: Text Search |
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2013-04-09 12:08:08 | [PATCH] pg_regress and non-default unix socket path |
Previous Message | Alexander Korotkov | 2013-04-09 08:58:21 | Re: WIP: index support for regexp search |