From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: transactoin id wraparound problem
Date: Wed, 06 Sep 2006 15:42:41 -0400
Message-ID: <23650.1157571761@sss.pgh.pa.us> (raw)
In-Reply-To: <20060906193208.GP362@phlogiston.dyndns.org>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local>
<20060906193208.GP362@phlogiston.dyndns.org>
Andrew Sullivan <ajs@crankycanuck.ca> writes:
> On Wed, Sep 06, 2006 at 12:23:01PM -0700, Sriram Dandapani wrote:
>> 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.
He's apparently running 8.1 (I don't think that error message wording
exists in older releases), so what would happen is that the DB will
refuse to start new transactions; but there won't be any data lost.
Still it might be best to let the vacuum have all the machine's cycles
to get done as fast as possible.
regards, tom lane
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: tgl@sss.pgh.pa.us, ajs@crankycanuck.ca
Subject: Re: transactoin id wraparound problem
In-Reply-To: <23650.1157571761@sss.pgh.pa.us>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local> <20060906193208.GP362@phlogiston.dyndns.org> <23650.1157571761@sss.pgh.pa.us>
* 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