From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Nick Rupley <nickr(at)mirthcorp(dot)com>, Nick Rupley <nickr(at)mirth(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index |
Date: | 2014-05-20 13:07:48 |
Message-ID: | 20140520130748.GA30841@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
On 2014-05-05 14:56:27 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Nick Rupley wrote:
> >> Not sure if this is relevant or not, but it looks like the duplicate rows
> >> continue to be inserted here and there on our production box (to which we
> >> haven't yet applied the hotfix). As I stated before that production box did
> >> have some server crashes before, but actually it hasn't had any recently
> >> (in the past week), and yet the duplicate rows continue to happen.
>
> > This bug is not dependent on a crash; the corruption occurs to the live
> > data. Only the previous bug mentioned by Tom manifested itself during
> > crash recovery.
>
> Hm. If people are hitting this in the field, do we need to think about
> yet another fairly-high-priority update release?
So, how about 9.3.5?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-05-20 13:12:04 | Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index |
Previous Message | Dhiraj Chawla | 2014-05-20 12:28:52 | Re: Re: [BUGS] BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password |