From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Russ Garrett <russ(at)garrett(dot)co(dot)uk> |
Cc: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org>, pgperf <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Invulnerable VACUUM process thrashing everything |
Date: | 2005-12-30 03:03:01 |
Message-ID: | 7577.1135911781@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Russ Garrett <russ(at)garrett(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Arup Dutta | 2005-12-30 07:01:29 | unsubscribe |
Previous Message | Jeffrey W. Baker | 2005-12-30 02:16:02 | Re: Invulnerable VACUUM process thrashing everything |