Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Autovacuum loose ends

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:42:41
Message-ID: 200507301442.j6UEgfR13357@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> "Michael Paesold" <mpaesold(at)gmx(dot)at> writes:
> > Alvaro Herrera wrote:
> >> I still haven't added custom cost-based delays, but I don't see that as
> >> a showstopper for removing it.  I just went through the CVS log and I
> >> don't see anything else that applies.
> 
> > 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.
> 
> It occurs to me that you could have that today, using the knowledge that
> the autovac daemon runs as the bootstrap user: use ALTER USER SET to
> attach user-specific vacuum delay settings to that role.  This is a
> pretty bletcherous solution, because (a) it requires knowledge of an
> undocumented implementation detail and (b) it would interfere with using
> that role for normal manual maintenance.  So I agree that a few extra
> GUC settings would be better.  But we could get away without 'em.
> 
> Along the same lines, it was suggested that we need a way to disable
> stats gathering on a per-database basis.  We already have it: you can
> use ALTER DATABASE SET to control stats_row_level and stats_block_level
> that way.  Neither of the above two objections apply to this usage, so
> I think we can mark off that wishlist item as "done".  (Of course, the
> soon-to-appear autovac documentation had better mention this trick.)

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.

-- 
  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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-07-30 14:51:08
Subject: Re: Updated open items
Previous:From: Tom LaneDate: 2005-07-30 14:37:57
Subject: Re: [HACKERS] Autovacuum loose ends

pgsql-patches by date

Next:From: Magnus HaganderDate: 2005-07-30 14:46:43
Subject: Re: Updated instrumentation patch
Previous:From: Magnus HaganderDate: 2005-07-30 14:39:12
Subject: Updated instrumentation patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group