From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: transactoin id wraparound problem
Date: Wed, 06 Sep 2006 14:38:19 -0500
Message-ID: <1157571499.20424.20.camel@state.g2switchworks.com> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local>
On Wed, 2006-09-06 at 14:23, Sriram Dandapani wrote:
> Thanks
>
> Is there a way to monitor vacuum progress. Can I resume normal
> operations assuming vacuum will update the transaction ids or should I
> wait till it finishes.
As Andrew mentioned, there's the possibility of wrapping before vacuum
finishes. Other than that, there's no danger to continuing to use the
db while it's being vacuumed.
There was a post here a little while back that had a query that would
show you how many transactions you had until wraparound and which
databases had been vacuumed when...
The basic data is in pg_database. Take a look at that table.
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: smarlowe@g2switchworks.com, sdandapani@counterpane.com, tgl@sss.pgh.pa.us
Subject: Re: transactoin id wraparound problem
In-Reply-To: <1157571499.20424.20.camel@state.g2switchworks.com>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local> <1157571499.20424.20.camel@state.g2switchworks.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