From: Tom Lane <tgl@sss.pgh.pa.us>
To: John R Pierce <pierce@hogranch.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
Date: Mon, 07 Jul 2014 19:14:53 -0400
Message-ID: <13414.1404774893@sss.pgh.pa.us> (raw)
In-Reply-To: <53BB25E4.5080400@hogranch.com>
References: <llqby44xt4iugpyxywv1ecdx.1404767140640@email.android.com>
<CAOf_bQbR8nLQ4-yJ9bqw8P980NeVJYVSeK=FTYJctazYr0kuWw@mail.gmail.com>
<53BB25E4.5080400@hogranch.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
John R Pierce <pierce@hogranch.com> writes:
> On 7/7/2014 2:14 PM, Prabhjot Sheena wrote:
>> i will run full vacuum than and see how it goes.
> do make sure there aren't any OLD pending transactions hanging around.
Not only regular transactions, but prepared transactions:
select * from pg_prepared_xacts;
8.3 was the last release in which max_prepared_transactions was nonzero
by default, thereby allowing people to shoot themselves in the foot
this way without having taken off the safety first :-(
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, pierce@hogranch.com, pgsql-general@postgresql.org
Subject: Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions
In-Reply-To: <13414.1404774893@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