Skip site navigation (1) Skip section navigation (2)

Vacuum Full Analyze Stalled

From: "Jeff Kirby" <Jeff(dot)Kirby(at)wicourts(dot)gov>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Vacuum Full Analyze Stalled
Date: 2005-10-02 16:42:35
Message-ID: s33fc7c0.010@gwmta.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
I'm going to attempt to do my best in describing the situation... so please forgive any ignorance on my part since I am very new to the Postgres community.

We have 2 identical Postgres databases, one on a Windows 2003 platform, and the other on a SUSe 9.3 Linux platform (both platforms have identical hardware).  They both have the same schema, the same configuration settings (as far as I can tell), and relatively the same amount of data (approx 32GB).  OK... here is the scoop, I started a "vacuum full analyze verbose" on both last night... the windows box completed in about 1 1/2 hours... 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.

So the question is... has anyone experienced this problem in the past?  If so, what do you recommend to rectify the problem?  Is it normal to be running for more than 12 hours on a table that only has 35 rows?  Do you need me to attach the log output thus far from both the Windows and Linux box?  Any help here would be greatly appreciated.  Any commands you can suggest to run on the Linux machine... no problem.

Jeffrey Kirby
CCAP Web Team
jeff(dot)kirby(at)wicourts(dot)gov
608-264-6253


Responses

pgsql-admin by date

Next:From: Uwe C. SchroederDate: 2005-10-02 23:04:22
Subject: Re: backup software for postgresql
Previous:From: Robert NgoDate: 2005-10-02 12:06:25
Subject: backup software for postgresql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group