| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Nick Rupley <nickr(at)mirthcorp(dot)com>, Andres Freund <andres(at)2ndquadrant(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-05 18:56:27 |
| Message-ID: | 19915.1399316187@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jamie Koceniak | 2014-05-05 19:37:26 | Re: BUG #9635: Wal sender process is using 100% CPU |
| Previous Message | Nick Rupley | 2014-05-05 18:31:16 | Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index |