| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Glen Parker <glenebob(at)nwlink(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: AutoVacuum on demand? |
| Date: | 2006-11-14 14:43:26 |
| Message-ID: | 4559D60E.20607@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Csaba Nagy wrote:
> [snip]
>
>> I think the idea is to edit the postgresql.conf file on the fly and send
>> a SIGHUP to the postmaster. I haven't ever heard of anyone doing that,
>> but I don't see any reason why it wouldn't work.
>>
>
> It works, I did it for a while with the statement_timeout to change it
> globally over night when admin tasks were running. For the
> statement_timeout thing it wasn't optimal however, finally I had to
> ditch the thing... but it can be done.
I'm confused, what does statement timeout have to do with this? I was
assuming you would edit "autovacuum = off" to "autovacuum = on" wouldn't
that work?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-11-14 14:51:15 | Re: libpq.so full name? |
| Previous Message | surabhi.ahuja | 2006-11-14 14:24:30 | libpq.so full name? |