From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | tamanna madaan <tamanna(dot)madan(at)globallogic(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, Tapin Agarwal <tapin(dot)agarwal(at)globallogic(dot)com> |
Subject: | Re: "attempted to lock invisible tuple" error while update |
Date: | 2010-07-14 20:47:20 |
Message-ID: | 1279140409-sup-3413@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Excerpts from Greg Smith's message of mié jul 14 09:52:46 -0400 2010:
> tamanna madaan wrote:
> > The same fix is not included in fix list for postgres-8.1.19 which came
> > at the same time when postgres-8.4.2 was released i.e 14th Dec.,2009.
> > Its not there in any of the 8.1 releases after that i.e 8.1.20 and 21.
> >
>
> See http://archives.postgresql.org/pgsql-committers/2009-10/msg00004.php
> ; that was a bug specific to 8.4 that shouldn't be present in the
> earlier versions.
Specifically, the bug was on code that didn't exist back in 8.1.
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2010-07-14 21:00:31 | Re: Index on a Decrypt / Bytea2Text Function |
Previous Message | Anthony Presley | 2010-07-14 20:31:10 | Re: Index on a Decrypt / Bytea2Text Function |