From: | Sebastian Kornehl <webmaster(at)sourcebase(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Reltuples/n_live_tup values wrong |
Date: | 2013-08-07 12:50:13 |
Message-ID: | 52024285.2030204@sourcebase.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi Tom,
thanks for your Reply!
You might be right, I found some pg_prepared_xacts from 2013-05-23. This
was a test with a XA using application, but the application is already
offline. There is also no pid available for the given transaction id's.
Do you have any idea how to close these xa transactions without
restarting the whole db?
Thank you.
-Sebastian
On 08/07/2013 02:12 PM, Tom Lane wrote:
> Sebastian Kornehl <webmaster(at)sourcebase(dot)org> writes:
>> I'm facing a problem which seems like a bug to me. I'm running:
> It seems like most of your problem is explained by this:
>
>>> DETAIL: 609299 dead row versions cannot be removed yet.
> You need to get rid of whatever old open transaction is preventing
> those rows from getting vacuumed away. Perhaps you have a prepared
> transaction lying around?
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2013-08-07 12:58:28 | Re: Reltuples/n_live_tup values wrong |
Previous Message | Tom Lane | 2013-08-07 12:12:55 | Re: Reltuples/n_live_tup values wrong |