X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id ECDE3D9DC5 for ; Sun, 2 Oct 2005 22:53:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 04538-03 for ; Mon, 3 Oct 2005 01:53:38 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 31D9AD9CCB for ; Sun, 2 Oct 2005 22:53:39 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j931rg5w010236; Sun, 2 Oct 2005 21:53:42 -0400 (EDT) To: "Jeff Kirby" Cc: pgsql-admin@postgresql.org Subject: Re: Vacuum Full Analyze Stalled In-reply-to: References: Comments: In-reply-to "Jeff Kirby" message dated "Sun, 02 Oct 2005 11:42:35 -0500" Date: Sun, 02 Oct 2005 21:53:42 -0400 Message-ID: <10235.1128304422@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200510/22 X-Sequence-Number: 19094 "Jeff Kirby" writes: > the Linux box however is still chugging away this morning... and > appears to be stuck on vacuuming "pg_constraint_contypid_index". How > do I know... well I don't really... I'm inferring based on the order > of the log output on the Windows box. Looking in pg_locks would give you a more reliable indicator of what the VACUUM is currently working on. Is the Linux box otherwise idle? There was another report recently of a vacuum hung up for a long time on pg_constraint_contypid_index, but it seemed to be due to extremely heavy usage of domain types ... regards, tom lane