From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions |
Date: | 2014-07-07 23:14:53 |
Message-ID: | 13414.1404774893@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
John R Pierce <pierce(at)hogranch(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David Morton | 2014-07-08 03:42:35 | Safe to gracefully switch 9.2 streaming replication roles multiple times ? |
Previous Message | John R Pierce | 2014-07-07 22:57:40 | Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions |
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Kumar | 2014-07-08 03:56:53 | Re: NOT IN and NOT EXIST |
Previous Message | John R Pierce | 2014-07-07 22:57:40 | Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions |