| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | tamanna madaan <tamanna(dot)madan(at)globallogic(dot)com> |
| Cc: | 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 21:22:17 |
| Message-ID: | AANLkTilXg0n8N22d91ZHgoscAV9E2iD3Y0FZqw6c6YKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 14, 2010 at 2:14 AM, tamanna madaan
<tamanna(dot)madan(at)globallogic(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Bartley | 2010-07-14 22:04:40 | Re: Redundant database objects. |
| Previous Message | Bill Moran | 2010-07-14 21:00:31 | Re: Index on a Decrypt / Bytea2Text Function |