I'm going to attempt to do my best in describing the situation... so please forgive any ignorance on my part since I am
verynew 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
(bothplatforms have identical hardware). They both have the same schema, the same configuration settings (as far as I
cantell), and relatively the same amount of data (approx 32GB). OK... here is the scoop, I started a "vacuum full
analyzeverbose" on both last night... the windows box completed in about 1 1/2 hours... the Linux box however is still
chuggingaway this morning... and appears to be stuck on vacuuming "pg_constraint_contypid_index". How do I know...
wellI 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
thelog output thus far from both the Windows and Linux box? Any help here would be greatly appreciated. Any commands
youcan suggest to run on the Linux machine... no problem.
Jeffrey Kirby
CCAP Web Team
jeff.kirby@wicourts.gov
608-264-6253
