From: Alvaro Herrera <alvherre@commandprompt.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: transactoin id wraparound problem
Date: Wed, 6 Sep 2006 22:47:50 -0400
Message-ID: <20060907024750.GN14024@alvh.no-ip.org> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC91A@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC91A@ca-mail1.cis.local>
Sriram Dandapani wrote:
> Hi
> I have several such databases to issue vacuum on. If I were to vacuum
> each table individually, would the transaction id be updated after every
> table vacuum.
No, you must issue database-wide vacuums. Single-table vacuums, even if
done to each and every table, do not suffice.
> Wonder if it is because I have several large partitioned tables that I
> drop every day that don't get vacuumed enough.
The best time of the day to do the vacuum would be just after one such
partition was dropped, one would think.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, sdandapani@counterpane.com, smarlowe@g2switchworks.com, tgl@sss.pgh.pa.us
Subject: Re: transactoin id wraparound problem
In-Reply-To: <20060907024750.GN14024@alvh.no-ip.org>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC91A@ca-mail1.cis.local> <20060907024750.GN14024@alvh.no-ip.org>
* 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