Re: PITR potentially broken in 9.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: PITR potentially broken in 9.2
Date: 2012-12-02 21:02:49
Message-ID: 7787.1354482169@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Sat, Dec 1, 2012 at 1:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm confused. Are you now saying that this problem only exists in
>> 9.1.x? I tested current HEAD because you indicated the problem was
>> still there.

> No, I'm saying the problem exists both in 9.1.x and in hypothetical
> 9.2.2 and in hypothetical 9.3, but not in 9.2.[01] because in those it
> is masked by that other problem which has just been fixed.

I'm still confused. I've now tried this in both HEAD and 9.1 branch
tip, and I do not see any misbehavior. If I set recovery_target_time to
before the pg_stop_backup time, I get "FATAL: requested recovery stop
point is before consistent recovery point" which is what I expect; and
if I set it to after the pg_stop_backup time, it starts up as expected.
So if there's a remaining unfixed bug here, I don't understand what
that is.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2012-12-03 06:05:57 Re: BUG #7722: extract(epoch from age(...)) appears to be broken
Previous Message aanisimov 2012-12-02 18:28:19 BUG #7722: extract(epoch from age(...)) appears to be broken

Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2012-12-02 21:23:34 Re: WIP: index support for regexp search
Previous Message Simon Riggs 2012-12-02 19:55:09 Re: [PATCH 08/14] Store the number of subtransactions in xl_running_xacts separately from toplevel xids