| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org>, Tony Wasson <ajwasson(at)gmail(dot)com>, Michael Fuhr <mike(at)fuhr(dot)org>, Luki Rustianto <lukirus(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: Is there a way to limit CPU usage per user |
| Date: | 2006-02-10 16:37:43 |
| Message-ID: | 20159.1139589463@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Csaba Nagy <nagy(at)ecircle-ag(dot)com> writes:
> How does this apply to autovacuum's long running vacuum commands ? Cause
> I have one table where the last vacuum took 15 hours :-)
[ Checks code... ] No, statement_timeout only applies to commands
arriving from an interactive client. This *would* be a hazard for
the contrib version of autovacuum, but not for the 8.1 integrated
version.
(If you're using contrib autovacuum, it'd be a good idea to do
"ALTER USER SET statement_timeout = 0" for the user it runs as.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob Pawley | 2006-02-10 17:02:11 | Tool |
| Previous Message | Csaba Nagy | 2006-02-10 16:10:59 | Re: Is there a way to limit CPU usage per user |