My goal is to reset the XID wraparound counter by performing vacuumdb
(autovacuum is not an option for my for various reasons)
On Sun, Nov 1, 2009 at 8:06 AM, Igor Polishchuk <ipolishchuk(at)hi5(dot)com> wrote:
> Why don't you just create a sql script with a separate vacuum command for
> each table you need to vacuum?
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org on behalf of Anj Adu
> Sent: Sun 11/1/2009 8:03 AM
> To: Alvaro Herrera
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] pg_autovacuum entries
> Does vacuumdb read pg_autovacuum ?
> If not, can I specify multiple comma-separated tables to pass as
> arguments to vacuumdb ? The list of tables that need to be vacuumed
> is a constant and hence easier to manage the vacuuming process.
> On Fri, Oct 30, 2009 at 3:04 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>> Anj Adu escribió:
>>> Is there a way to create an entry for a table that does not exist yet?
>> No, you will have to have "INSERT INTO pg_autovacuum" statements
>> alongside your table creation. I don't see that this is a lot of
>> trouble though, you can simply do
>> CREATE TABLE whatever ( ... );
>> INSERT INTO pg_autovacuum VALUES ('whatever'::regclass, false, -1, -1,
>> Alvaro Herrera
>> The PostgreSQL Company - Command Prompt, Inc.
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-admin by date
|Next:||From: Kevin Kempter||Date: 2009-11-01 17:22:20|
|Subject: dupes for PK and other UNIQUE indexes|
|Previous:||From: Igor Polishchuk||Date: 2009-11-01 16:06:07|
|Subject: Re: pg_autovacuum entries|