| 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-13 07:44:08 |
| Message-ID: | AANLkTilYV2pRN3ZM9lCWRbWPqwLGc7nCOABIY8_JhAcs@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 12, 2010 at 11:54 PM, tamanna madaan
<tamanna(dot)madan(at)globallogic(dot)com> wrote:
> Hi Scott
>
> Thanks for your reply . I haven't yet tried updating to latest 8.1.x version. Was juss googling about this error and came across
> a link discussing the same issue :
>
> http://groups.google.com/group/pgsql.general/browse_thread/thread/75df15648bcb502b/10232d1f183a640a?lnk=raot
>
> In this , the problem had occurred on 8.4.1 and a patch (snapmgr-bugfix-rehash-2.patch ) was provided on 8.4.1 to circumvent this problem.
>
> This patch worked fine . I was just wondering if this patch
> is backward compatible and can it be merged with 8.1.2
> to get it working. Any suggestions ??
Check the release notes for the 8.1 version that came our around the
same time as 8.4.2? I'd expect if it's a known issue that affected
all versions the fix got put into the older versions as well, unless
it was considered a more dangerous thing to fix there.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-07-13 07:45:12 | Re: PG_DUMP very slow because of STDOUT ?? |
| Previous Message | Pavel Stehule | 2010-07-13 07:05:43 | Re: Redundant database objects. |