Re: "attempted to lock invisible tuple" error while update - Mailing list pgsql-general

From Scott Marlowe
Subject Re: "attempted to lock invisible tuple" error while update
Date
Msg-id AANLkTilXg0n8N22d91ZHgoscAV9E2iD3Y0FZqw6c6YKQ@mail.gmail.com
Whole thread Raw
In response to Re: "attempted to lock invisible tuple" error while update  ("tamanna madaan" <tamanna.madan@globallogic.com>)
List pgsql-general
On Wed, Jul 14, 2010 at 2:14 AM, tamanna madaan
<tamanna.madan@globallogic.com> wrote:
> Hi Scott
>
> I looked into the release notes of 8.4.2 and found the following fix in
> the fix list for 8.4.2 :

Your first priority should be updating to the latest 8.1 version
available.  While it may or may not have had release notes made about
it, it's quite likely you're being bitten by a fixed bug.  Why torture
yourself?  Pgsql is the best package of any bit of kit I've ever used
about NOT introducing new and broken things in updates.  Upgrade to
8.1.latest first.

pgsql-general by date:

Previous
From: Bill Moran
Date:
Subject: Re: Index on a Decrypt / Bytea2Text Function
Next
From: Andrew Bartley
Date:
Subject: Re: Redundant database objects.