| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PITR potentially broken in 9.2 |
| Date: | 2012-11-28 04:27:28 |
| Message-ID: | 20121128042728.GB26990@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Tue, Nov 27, 2012 at 10:08:12AM -0800, Jeff Janes wrote:
> Doing PITR in 9.2.1, the system claims that it reached a consistent
> recovery state immediately after redo starts.
> This leads to it various mysterious failures, when it should instead
> throw a "requested recovery stop point is before consistent recovery
> point" error.
> (If you are unlucky, I think it might even silently start up in a
> corrupt state.)
I observed a similar problem with 9.2. Despite a restore_command that failed
every time, startup from a hot backup completed. At the time, I suspected a
mistake on my part.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-11-28 13:15:56 | Re: PITR potentially broken in 9.2 |
| Previous Message | tarvip | 2012-11-27 19:52:09 | BUG #7710: Xid epoch is not updated properly during checkpoint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-28 04:46:58 | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |
| Previous Message | Bruce Momjian | 2012-11-28 04:13:04 | Re: Further pg_upgrade analysis for many tables |