pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Kempter <kevin@kevinkempterllc.com>
To: pgsql-admin@postgresql.org
Subject: Re: Get a list of ALL tables
Date: Mon, 19 Nov 2007 16:41:10 -0700
Message-ID: <200711191641.10792.kevin@kevinkempterllc.com> (raw)
In-Reply-To: <8053.1195514955@sss.pgh.pa.us>
References: <200711191524.47852.kevin@kevinkempterllc.com>
	<8053.1195514955@sss.pgh.pa.us>

Sorry, I meant to send this to the list:


We have a handful of tables that are quite large and take several hours to 
vacuum. We're managing these large tables by using cron via a schedule that 
accounts for system load. I want to pull the list of all tables and exclude 
these large tables from the list, then run the vacuum on the remaining tables 
once a week to avoid transaction ID wraparound failures.


/Kevin




> Kevin Kempter <kevin@kevinkempterllc.com> writes:
> > I'm working with a client with several highly active 8.1.4 servers. I
> > want to run a weekly cron that will vacuum ALL db tables except those
> > with entries in pg_autovacuum (where we've setup manual/cron vacuums) in
> > order to eliminate transaction ID wraparound failure warnings (which
> > comes up fairly often).
> >
> > My question is:
> > will a select from pg_tables for each database in the cluster provide me
> > with a full table listing for the purposes of ensuring that all tables in
> > the db have been vacuumed or are there others I'll need to account for as
> > well ?
>
> Why are you insisting on inventing your own wheel for this, when
> "vacuum" without a parameter does that just fine?
>
>                       regards, tom lane




On Monday 19 November 2007 16:29:15 you wrote:
> Kevin Kempter <kevin@kevinkempterllc.com> writes:
> > I'm working with a client with several highly active 8.1.4 servers. I
> > want to run a weekly cron that will vacuum ALL db tables except those
> > with entries in pg_autovacuum (where we've setup manual/cron vacuums) in
> > order to eliminate transaction ID wraparound failure warnings (which
> > comes up fairly often).
> >
> > My question is:
> > will a select from pg_tables for each database in the cluster provide me
> > with a full table listing for the purposes of ensuring that all tables in
> > the db have been vacuumed or are there others I'll need to account for as
> > well ?
>
> Why are you insisting on inventing your own wheel for this, when
> "vacuum" without a parameter does that just fine?
>
> 			regards, tom lane





view thread (6+ messages)  latest in thread

Message-ID: <200711191641.10792.kevin@kevinkempterllc.com>
Permalink:  ../200711191641.10792.kevin@kevinkempterllc.com/
Also on:    postgresql.org/message-id/200711191641.10792.kevin@kevinkempterllc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: kevin@kevinkempterllc.com
  Subject: Re: Get a list of ALL tables
  In-Reply-To: <200711191641.10792.kevin@kevinkempterllc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox