| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Nice vacuums |
| Date: | 2004-10-22 18:53:43 |
| Message-ID: | 16984.1098471223@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
> Tom Lane wrote:
>> What *would* be useful is an option to turn on the 8.0 vacuum cost delay
>> features (ie, set non-default values for those GUC variables).
>>
> Just curious, if I were to submit patches in the next week or so that
> added new command line options to pg_autovacuum that corresponded to the
> new vacuum cost delay features, would they still be accepted? I know we
> are well into beta, but it's also a contrib module, and the changes
> would be pretty simple.
I would be inclined to accept it, since the cost-delay feature certainly
needs to play nicely with autovacuum. I was actually surprised to
discover this hadn't been done already.
If you could get it done today or tomorrow so we can fit it into beta4,
that would be even better ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-10-22 19:13:16 | Re: code question: storing INTO relation |
| Previous Message | Simon Riggs | 2004-10-22 18:50:59 | ARC Memory Usage analysis |