| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
| Cc: | Justin Clift <justin(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [pgsql-www] pg_autovacuum is nice ... but ... |
| Date: | 2004-11-04 22:44:32 |
| Message-ID: | 6789.1099608272@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
"Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> Moved to -hackers where this belongs :)
> On Fri, 5 Nov 2004, Justin Clift wrote:
>> Would making max_fsm_relations and max_fsm_pages dynamically update
>> themselves whilst PostgreSQL runs be useful?
Possibly, but it isn't happening in the foreseeable future, for the same
reason that we don't auto-update shared_buffers and the other shared
memory sizing parameters: we can't resize shared memory on the fly.
> I'm not sure if I like this one too much ... but it would be nice if
> something like this triggered a warning in the logs, maybe a feature of
> pg_autovacuum itself?
autovacuum would probably be a reasonable place to put it. We don't
currently have any good way for autovacuum to get at the information,
but I suppose that an integrated autovacuum daemon could do so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2004-11-04 22:54:19 | Re: CVS should die |
| Previous Message | Marc G. Fournier | 2004-11-04 22:26:08 | Re: [pgsql-www] pg_autovacuum is nice ... but ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GUNDUZ | 2004-11-04 22:57:02 | Re: New Event |
| Previous Message | Marc G. Fournier | 2004-11-04 22:26:08 | Re: [pgsql-www] pg_autovacuum is nice ... but ... |