| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paesold <mpaesold(at)gmx(dot)at>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Autovacuum loose ends |
| Date: | 2005-07-30 14:57:15 |
| Message-ID: | 200507301457.j6UEvFR20670@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >>> I think you should at least add an autovacuum specific value for
> >>> "vacuum_cost_delay" because it turns cost-based vacuum delay on or off.
>
> > I am thinking we should move ahead with what we have now, suggest the
> > work-arounds, and thensee what use-cases we have for it for later
> > releases.
>
> I think it's absolutely unquestionable that there is a use-case for
> running autovac with different vacuum-delay settings than you would
> want to apply to manually issued vacuums. We don't need to wait for
> field experience on that one; we already have it with the contrib
> version.
So do we need to add new GUC variables?
--
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 | Bruce Momjian | 2005-07-30 15:17:03 | Re: Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL |
| Previous Message | Tom Lane | 2005-07-30 14:55:33 | Re: [HACKERS] Autovacuum loose ends |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-30 15:07:44 | Re: Updated instrumentation patch |
| Previous Message | Tom Lane | 2005-07-30 14:55:33 | Re: [HACKERS] Autovacuum loose ends |