| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Naoya Anzai <anzai-naoya(at)mxu(dot)nes(dot)nec(dot)co(dot)jp>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Akio Iwaasa <iwaasa(at)mxs(dot)nes(dot)nec(dot)co(dot)jp> |
| Subject: | Re: Table-level log_autovacuum_min_duration |
| Date: | 2015-03-23 15:34:21 |
| Message-ID: | 1392.1427124861@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Mon, Mar 23, 2015 at 7:07 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah, checking for SIGHUP in the worker outer loop (ie once per table)
>> seems like a reasonable thing.
> Could it be done more often? Maybe every time it is about to do a
> cost_delay sleep?
That sounds risky from here. Normal backends don't check it more often
than once per command.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-03-23 15:48:21 | Re: Superuser connect during smart shutdown |
| Previous Message | Bruce Momjian | 2015-03-23 15:33:22 | Re: Zero-padding and zero-masking fixes for to_char(float) |