From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [BUGS] PITR potentially broken in 9.2 |
Date: | 2012-12-05 09:50:12 |
Message-ID: | CA+U5nMJN_TCkeQfgGmuHzOejVyjYtEtgbf1Y5yz9Aog2xh+06Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 5 December 2012 00:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> So apparently this is something we broke since Nov 18. Don't know what
>> yet --- any thoughts?
>
> Further experimentation shows that reverting commit
> ffc3172e4e3caee0327a7e4126b5e7a3c8a1c8cf makes it work. So there's
> something wrong/incomplete about that fix.
>
> This is a bit urgent since we now have to consider whether to withdraw
> 9.2.2 and issue a hasty 9.2.3. Do we have a regression here since
> 9.2.1, and if so how bad is it?
I'll look at this now.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2012-12-05 10:06:55 | Re: PITR potentially broken in 9.2 |
Previous Message | JEHAD GHAREEB | 2012-12-05 06:49:34 | Installing PG 7.3.4 on Linux 6 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2012-12-05 10:06:55 | Re: PITR potentially broken in 9.2 |
Previous Message | John R Pierce | 2012-12-05 09:46:11 | Re: ALTER TABLE ... NOREWRITE option |