On Wed, Jul 14, 2010 at 2:14 AM, tamanna madaan
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
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
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-
.marl...@gmail.com]
Sent: Tuesday, July 13, 2010 1:14 PM
To: tamanna madaan
Cc: pgsql-general@postgresql.org; Tapin Agarwal
Subject: Re: [GENERAL] "attempted to lock invisible tuple" error while
update
On Mon, Jul 12, 2010 at 11:54 PM, tamanna madaan
wrote:
> Hi Scott
>
> Thanks fo
On Mon, Jul 12, 2010 at 11:54 PM, tamanna madaan
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_th
manna
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Friday, July 09, 2010 9:35 PM
To: tamanna madaan
Cc: pgsql-general@postgresql.org; Tapin Agarwal
Subject: Re: [GENERAL] "attempted to lock invisible tuple" error while update
On Thu, Jul 8, 2
On Thu, Jul 8, 2010 at 10:56 PM, tamanna madaan
wrote:
> Hi All
>
> I am using a cluster setup with two nodes in it. Replication between two
> nodes is being done through slony.
>
> Postgres version is 8.1.2 and slony version is 1.1.5 .
>
> I am running an operation that does thousands of update
Hi All
I am using a cluster setup with two nodes in it. Replication between
two nodes is being done through slony.
Postgres version is 8.1.2 and slony version is 1.1.5 .
I am running an operation that does thousands of update/inserts/delete
on some tables. While running update query on
