From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
Cc: | Jan Wieck <JanWieck(at)yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: VACUUM DELAY |
Date: | 2004-08-10 02:05:55 |
Message-ID: | 200408100205.i7A25tb00362@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gaetano Mendola wrote:
> However I think is annoying to write:
>
> set vacuum_cost_delay = 100;
> vacuum table <big_huge>;
> set vacuum_cost_delay = 0;
> set <whatelse>;
> vacuum table <night_table>;
> ....
> ....
Well, you are already seting it to zero for night, so why not just set
it to non-zero for day? Seems the same to me, or set it to non-zero in
postgresql.conf and set it to zero at night.
> or even better:
>
> psql -c "set vacuum_cost_delay = 100; vacuum analyze;"
>
> and what about the utility vacuumdb ?
Anyone using the utility command can use PGOPT to set the GUC I think.
Maybe we should mention that in the manual page.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Brown | 2004-08-10 02:13:00 | Re: Tablespace issues (comment on ,moving indexes) |
Previous Message | Tom Lane | 2004-08-10 02:04:53 | Re: PITR - Some data is not recovered. |