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 02898D9DA7 for ; Mon, 3 Oct 2005 10:18:00 -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 01231-09 for ; Mon, 3 Oct 2005 13:17:54 +0000 (GMT) Received: from gwmta.wicourts.gov (gwmta2.wicourts.gov [165.219.244.92]) by svr1.postgresql.org (Postfix) with ESMTP id E07A4D9D66 for ; Mon, 3 Oct 2005 10:17:53 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Mon, 03 Oct 2005 08:17:53 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Mon, 03 Oct 2005 08:17:36 -0500 From: "Jeff Kirby" To: Cc: Subject: Re: Vacuum Full Analyze Stalled Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 required=5 tests=[none] X-Spam-Level: X-Archive-Number: 200510/66 X-Sequence-Number: 19138 Thanks Tom...=20 The Linux box was completely idle (as you already guessed). There were = multiple locks on the table(s) in question. And to answer your question, = we are heavily using domain types. I suspect (to refresh your memory) = that the problem reported earlier was from Kevin Grittner. Do you know if = there are any plans to have better utilization of domain types in = Postgres? The steps I took to resolve the problem was to completely kill all = processes, restarted the Postgres service, and then ran "vacuum full = analyze" upon a successful restart. That went through without a hitch. = =20 Thanks again... let me know if you can think of anything that could/would = prevent this problem in the future (outside of eliminating domain types). Jeff Kirby >>> Tom Lane 10/02/05 8:53 PM >>> "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