From: Craig Ringer <ringerc@ringerc.id.au>
To: Nimesh Satam <nimesh.zedo@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Vacuum problems with 9.1
Date: Tue, 28 Aug 2012 14:53:54 +0800
Message-ID: <503C6B02.5070104@ringerc.id.au> (raw)
In-Reply-To: <CACemtiN4fMC1Xgbuh=Tdr7fWP_4GqLgYnd=nacz9xHbH7VDFMQ@mail.gmail.com>
References: <CACemtiN4fMC1Xgbuh=Tdr7fWP_4GqLgYnd=nacz9xHbH7VDFMQ@mail.gmail.com>
On 08/28/2012 12:33 PM, Nimesh Satam wrote:
> Hi,
>
> We have been using the current version of postgres i.e. 9.1.4 with
> streaming replication on. While vacuuming we noticed that certain dead
> rows are not getting removed and following debug information is printed:
>
> "DETAIL: 12560 dead row versions cannot be removed yet."
>
> As per suggestion, we made sure that no long running transactions are
> active. Also all the applications were stopped during this time.
>
> Can anybody highlight the possible reason for the dead rows not been
> cleaned?
I don't know if prepared transactions could cause this exact message,
but check:
select * from pg_prepared_xacts ;
to see if you have any prepared transactions (from two-phase commit)
lying around.
If you don't use XA or 2PC, consider setting max_prepared_transactions
to 0 in postgresql.conf if it isn't already.
--
Craig Ringer
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-performance@postgresql.org
Cc: ringerc@ringerc.id.au, nimesh.zedo@gmail.com
Subject: Re: Vacuum problems with 9.1
In-Reply-To: <503C6B02.5070104@ringerc.id.au>
* 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