| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Autovacuum cancellation |
| Date: | 2007-10-26 12:59:47 |
| Message-ID: | 10623.1193403587@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers pgsql-patches |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> I assume the right thing happens if multiple deadlock check signals fire for
> the same autovacuum?
Multiple signals shouldn't be a problem, but late-arriving ones could be.
It might be worth having autovac explicitly clear QueryCancelPending
after it's finished a table, so that a SIGINT sent because of activity
on one table couldn't force cancellation of vacuum on the next one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-26 13:30:10 | pgsql: Avoid including any backend-only stuff in the zic utility |
| Previous Message | Tom Lane | 2007-10-26 12:56:37 | Re: Autovacuum cancellation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2007-10-26 13:01:14 | Re: PANIC caused by open_sync on Linux |
| Previous Message | Tom Lane | 2007-10-26 12:56:37 | Re: Autovacuum cancellation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-26 13:32:41 | Re: fix ZIC dependency on postgres.h |
| Previous Message | Tom Lane | 2007-10-26 12:56:37 | Re: Autovacuum cancellation |