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
In-reply-to: <53BB25E4.5080400@hogranch.com>
References: <llqby44xt4iugpyxywv1ecdx.1404767140640@email.android.com>
 <CAOf_bQbR8nLQ4-yJ9bqw8P980NeVJYVSeK=FTYJctazYr0kuWw@mail.gmail.com>
 <53BB25E4.5080400@hogranch.com>
Comments: In-reply-to John R Pierce <pierce@hogranch.com>
 message dated "Mon, 07 Jul 2014 15:57:40 -0700"
Date: Mon, 07 Jul 2014 19:14:53 -0400
Message-ID: <13414.1404774893@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

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