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

Re: Interface for pg_autovacuum

From: "Jim Nasby" <jim(dot)nasby(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Dave Page" <dpage(at)postgresql(dot)org>,"Florian G(dot) Pflug" <fgp(at)phlo(dot)org>,"PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Interface for pg_autovacuum
Date: 2006-12-21 18:10:08
Message-ID: 7C4D872D-7172-40AA-8104-A5AE4241048E@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
How about...

ALTER TABLE ...
ALTER AUTOVACUUM [ THRESHOLD | SCALE | COST DELAY | COST LIMIT ]
ALTER AUTOANALYZE [ THRESHOLD | SCALE ]

... or would that create a whole bunch of reserved words?

On Dec 21, 2006, at 10:04 AM, Simon Riggs wrote:

> On Wed, 2006-12-20 at 09:47 -0500, Jim Nasby wrote:
>
>> On the other hand, this would be the only part of the system where
>> the official interface/API is a system catalog table. Do we really
>> want to expose the internal representation of something as our API?
>> That doesn't seem wise to me...
>
> Define and agree the API (the hard bit) and I'll code it (the easy  
> bit).
>
> We may as well have something on the table, even if it changes later.
>
> Dave: How does PgAdmin handle setting table-specific autovacuum
> parameters? (Does it?)
>
> -- 
>   Simon Riggs
>   EnterpriseDB   http://www.enterprisedb.com
>
>
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
>                 http://www.postgresql.org/about/donate
>

--
Jim Nasby                               jim(dot)nasby(at)enterprisedb(dot)com
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




In response to

Responses

pgsql-hackers by date

Next:From: Gregory StarkDate: 2006-12-21 18:20:41
Subject: Re: Interface for pg_autovacuum
Previous:From: Alvaro HerreraDate: 2006-12-21 17:41:32
Subject: Re: Autovacuum Improvements

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