From: Tom Lane <tgl@sss.pgh.pa.us>
To: Russ Garrett <russ@garrett.co.uk>
Cc: Jeffrey W. Baker <jwbaker@acm.org>
Cc: pgperf <pgsql-performance@postgresql.org>
Subject: Re: Invulnerable VACUUM process thrashing everything
Date: Thu, 29 Dec 2005 22:03:01 -0500
Message-ID: <7577.1135911781@sss.pgh.pa.us> (raw)
In-Reply-To: <43B468D7.2050806@garrett.co.uk>
References: <1135894162.2223.4.camel@toonses.gghcwest.com>
<6.2.5.6.0.20051229173718.01dbfff0@earthlink.net>
<43B468D7.2050806@garrett.co.uk>
Russ Garrett <russ@garrett.co.uk> writes:
> VACUUM *will* respond to a SIGTERM, but it doesn't check very often -
> I've often had to wait hours for it to determine that it's been killed,
> and my tables aren't anywhere near 1TB. Maybe this is a place where
> things could be improved...
Hmm, there are CHECK_FOR_INTERRUPTS calls in all the loops that seem
significant to me. Is there anything odd about your database schema?
Unusual index types or data types maybe? Also, what PG version are
you using?
If you notice a VACUUM not responding to SIGTERM promptly, it'd be
useful to attach to the backend process with gdb and get a stack trace
to find out what it's doing.
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, russ@garrett.co.uk, jwbaker@acm.org
Subject: Re: Invulnerable VACUUM process thrashing everything
In-Reply-To: <7577.1135911781@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