Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A31122E003C for ; Mon, 19 Nov 2007 19:29:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 74912-05 for ; Mon, 19 Nov 2007 19:29:17 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 07E982E0032 for ; Mon, 19 Nov 2007 19:29:17 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lAJNTFEk008054; Mon, 19 Nov 2007 18:29:15 -0500 (EST) To: Kevin Kempter cc: pgsql-admin@postgresql.org Subject: Re: Get a list of ALL tables In-reply-to: <200711191524.47852.kevin@kevinkempterllc.com> References: <200711191524.47852.kevin@kevinkempterllc.com> Comments: In-reply-to Kevin Kempter message dated "Mon, 19 Nov 2007 15:24:47 -0700" Date: Mon, 19 Nov 2007 18:29:15 -0500 Message-ID: <8053.1195514955@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/180 X-Sequence-Number: 27423 Kevin Kempter 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