From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kim <kim@myemma.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: unusual performance for vac following 8.2 upgrade
Date: Thu, 11 Jan 2007 13:17:44 -0500
Message-ID: <27678.1168539464@sss.pgh.pa.us> (raw)
In-Reply-To: <45A671CD.1050706@myemma.com>
References: <45A671CD.1050706@myemma.com>
Kim <kim@myemma.com> writes:
> Running a vac on an 8.2 client connecting to an 8.2 database (following
> example was for a 14 row static table) - vacuums will sit (for lack of a
> better word) for anywhere from ten to twenty minutes before taking a
> lock out on the table and doing work there.
How big is this database (how many pg_class entries)? What do you get
from "VACUUM VERBOSE pg_class"? The truss results make it sound like
the problem is pgstat_vacuum_tabstat() taking a long time, but that code
has not changed since 8.1 ...
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, kim@myemma.com
Subject: Re: unusual performance for vac following 8.2 upgrade
In-Reply-To: <27678.1168539464@sss.pgh.pa.us>
* 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