Re: PITR potentially broken in 9.2

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PITR potentially broken in 9.2
Date: 2012-11-28 14:38:40
Message-ID: 20121128143840.GA27189@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 2012-11-28 16:34:55 +0200, Heikki Linnakangas wrote:
> On 28.11.2012 15:47, Andres Freund wrote:
> >I mean the label read by read_backup_label(). Jeff's mail indicated it
> >had CHECKPOINT_LOCATION at 1/188D8120 but redo started at 1/CD89E48.
>
> That's correct. The checkpoint was at 1/188D8120, but it's redo pointer was
> earlier, at 1/CD89E48, so that's where redo had to start.

Heh. I I just compared 18 with CD and didn't notice the different length
of both...

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-11-28 15:51:08 Re: PITR potentially broken in 9.2
Previous Message Heikki Linnakangas 2012-11-28 14:34:55 Re: PITR potentially broken in 9.2

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit kapila 2012-11-28 14:47:44 Re: Proposal for Allow postgresql.conf values to be changed via SQL
Previous Message Heikki Linnakangas 2012-11-28 14:34:55 Re: PITR potentially broken in 9.2