From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Where do we stand on 9.3 bugs? |
Date: | 2014-01-14 02:19:59 |
Message-ID: | 26671.1389665999@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-01-13 17:30:55 -0800, Josh Berkus wrote:
>> Despite actually dating back to 9.0, something in the 9.3.2/9.2.6
>> updates is causing users to hit it now. And for those who do hit it,
>> replication is impossible and there's no workaround.
> There have been reports about it for years if you search in the archives
> and the code around it hasn't changed for a fair bit of time, so I think
> that's just coincidence.
I looked at the commit history for 9.2 post-release, and I don't see
anything that looks related, so I also doubt the theory that some recent
change has increased the odds of this happening. I think it's more that
we now recognize the cause of what previously seemed random breakage.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2014-01-14 02:25:17 | Re: GIN improvements part 1: additional information |
Previous Message | Tom Lane | 2014-01-14 01:59:48 | Re: Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages |