pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Kirby <Jeff.Kirby@wicourts.gov>
To: tgl@sss.pgh.pa.us
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum Full Analyze Stalled
Date: Mon, 03 Oct 2005 08:17:36 -0500
Message-ID: <s340e931.008@gwmta.wicourts.gov> (raw)

Thanks Tom... 

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.  

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 <tgl@sss.pgh.pa.us> 10/02/05 8:53 PM >>>
"Jeff Kirby" <Jeff.Kirby@wicourts.gov> 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




view thread (17+ messages)  latest in thread

Message-ID: <s340e931.008@gwmta.wicourts.gov>
Permalink:  ../s340e931.008@gwmta.wicourts.gov/
Also on:    postgresql.org/message-id/s340e931.008@gwmta.wicourts.gov

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Jeff.Kirby@wicourts.gov, tgl@sss.pgh.pa.us
  Subject: Re: Vacuum Full Analyze Stalled
  In-Reply-To: <s340e931.008@gwmta.wicourts.gov>
  References: <s340e931.008@gwmta.wicourts.gov>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox