X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7A81BD1B55F for ; Tue, 27 Jan 2004 21:48:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 80710-10 for ; Tue, 27 Jan 2004 17:48:23 -0400 (AST) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by svr1.postgresql.org (Postfix) with ESMTP id 1E566D1E1CF for ; Tue, 27 Jan 2004 17:41:46 -0400 (AST) Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 27 Jan 2004 13:44:09 -0800 Received: from cjwhitew2k02 (dhcp-128-107-151-36.cisco.com [128.107.151.36]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i0RLfj5k008925; Tue, 27 Jan 2004 13:41:45 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Tue, 27 Jan 2004 13:41:45 -0800 Message-ID: <004601c3e51e$5c750ba0$0b00a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <28344.1075238139@sss.pgh.pa.us> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/255 X-Sequence-Number: 12118 Cut and pasted from my screen to the e-mail. I did shutdown postmaster prior to running postgres standalone. I assume that quit from postgres backend stops it. I did restart postmaster prior running the psql vacuum full. Sorry, forgot to run verbose mode on the commands. I have re-initialized the DB and restored from a backup. Will send info if it happens again. Thanks for the help Chris -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, January 27, 2004 1:16 PM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White \(cjwhite\)" writes: > Here is the info. I am running 7.2.1. 7.2.1 is a bit long in the tooth; you really ought to be running 7.2.4 if you are still in the 7.2 series. However I don't think that has much to do with your immediate problem. The only thing that struck me about your transcript is that you didn't show shutting down and restarting the postmaster. You didn't try to run a standalone backend concurrently with the postmaster did you? (There are supposed to be interlocks against that, but maybe they failed.) The failures sort of look like the standalone backend's changes did not completely propagate back to the regular database, and that's the only very plausible mechanism I can think of for that ... Also, I really wanted to see the output of vacuum verbose. Just "vacuum" doesn't tell anything much. regards, tom lane