From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: transactoin id wraparound problem
Date: Wed, 6 Sep 2006 15:32:08 -0400
Message-ID: <20060906193208.GP362@phlogiston.dyndns.org> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local>
On Wed, Sep 06, 2006 at 12:23:01PM -0700, 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.
That depends on how many transactions you think will happen while
vacuum is running. If it's a lot, you could pass the fatal point (==
you lose data) before vacuum finishes. In most cases, it's probably
ok, but only you can decide how dangerous it would be for you to lose
data.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well.
--Dennis Ritchie
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: ajs@crankycanuck.ca
Subject: Re: transactoin id wraparound problem
In-Reply-To: <20060906193208.GP362@phlogiston.dyndns.org>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local> <20060906193208.GP362@phlogiston.dyndns.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