X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9B3BF9DC9B6 for ; Tue, 7 Mar 2006 11:34:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 45530-09 for ; Tue, 7 Mar 2006 11:34:35 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id D6DF39DC87E for ; Tue, 7 Mar 2006 11:34:28 -0400 (AST) Received: from andyshellam-gw.adsl.newnet.co.uk ([80.175.198.137]:1230 helo=acsdesk1) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1FGeCm-0007uP-AF; Tue, 07 Mar 2006 15:34:32 +0000 Reply-To: From: "Andy Shellam" To: Cc: Subject: Re: VACUUM Error? Date: Tue, 7 Mar 2006 15:34:29 -0000 Organization: the mail network MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01C641FC.9FD331A0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: thread-index: AcZB+2jz21XnLkPeSO2x5Gb4+yK8uAAAO2Ig Message-Id: <20060307153428.D6DF39DC87E@postgresql.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.647 required=5 tests=[AWL=-0.407, HTML_MESSAGE=0.001, HTML_TAG_EXIST_TBODY=0.126, MSGID_FROM_MTA_ID=0.927] X-Spam-Score: 0.647 X-Spam-Level: X-Archive-Number: 200603/68 X-Sequence-Number: 20825 This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C641FC.9FD331A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit If you do "ps auxwww|grep postgres" on your console command line - you should find processes with a status of "IDLE IN TRANSACTION" or similar, and use that data and the PG server status to identify where it came from, and submit a COMMIT or ROLLBACK command on that connection. _____ From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Fabrice.Sznajderman@devoteam.com Sent: Tuesday, 07 March, 2006 3:25 pm To: pgsql-admin@postgresql.org Subject: Re: [ADMIN] VACUUM Error? Hello Tom Lane, Thank you very much for your answer!! My PG version is older than 7.3 , I know it so old and so much old.. but I can't update this version... :-(( However, could you explain me how I can close open transaction? Thanks in advance!! best regard Fabrice Tom Lane 07/03/2006 15:52 A Fabrice.Sznajderman@devoteam.com cc pgsql-admin@postgresql.org Objet Re: [ADMIN] VACUUM Error? Fabrice.Sznajderman@devoteam.com writes: > But I had error :"ERROR: Parent tuple was not found What PG version is this? We recently fixed some bugs that could lead to this error. The error could only occur if you have some old open transaction(s) that could possibly still see since-updated tuples in the vacuumed table. So it'll go away if you close out open transactions. regards, tom lane !DSPAM:14,440da5fc49411673628609! ------=_NextPart_000_0003_01C641FC.9FD331A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
If you do "ps auxwww|grep postgres" on your = console command=20 line - you should find processes with a status of "IDLE IN TRANSACTION" = or=20 similar, and use that data and the PG server status to identify = where it=20 came from, and submit a COMMIT or ROLLBACK command on that=20 connection.


From: = pgsql-admin-owner@postgresql.org=20 [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of=20 Fabrice.Sznajderman@devoteam.com
Sent: Tuesday, 07 March, = 2006=20 3:25 pm
To: pgsql-admin@postgresql.org
Subject: Re: = [ADMIN]=20 VACUUM Error?


Hello Tom Lane, =

Thank you very much for your answer!!=20

My PG version is older than 7.3 = , I know it=20 so old and so much old.. but I can't update this version... :-((=20

However, could you explain me = how I can=20 close  open transaction?

Thanks=20 in advance!!

best = regard=20


Fabrice


Tom Lane=20 <tgl@sss.pgh.pa.us>

07/03/2006 15:52

A
Fabrice.Sznajderman@devoteam.com=20
cc
pgsql-admin@postgresql.org=20
Objet
Re: [ADMIN] = VACUUM=20 Error?

=




Fabrice.Sznajderman@devoteam.com writes:
> But I had = error=20 :"ERROR:  Parent tuple was not found

What PG version is = this?=20  We recently fixed some bugs that could lead to
this = error.

The=20 error could only occur if you have some old open transaction(s) = that
could=20 possibly still see since-updated tuples in the vacuumed table.
So = it'll go=20 away if you close out open transactions.

      =  =20                     =  =20                     = regards,=20 tom lane

!DSPAM:14,440da5fc49411673628609! = ------=_NextPart_000_0003_01C641FC.9FD331A0--