Re: [GENERAL] Modified rows are not marked as dead and as such vacuumis unable to clean them up - Mailing list pgsql-general

From Tamás András Kálmán
Subject Re: [GENERAL] Modified rows are not marked as dead and as such vacuumis unable to clean them up
Date
Msg-id CAAV1k2fJT9U3a55kQWmVR_8Yvn88DVGfdSZT98nooNcthe06CQ@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Modified rows are not marked as dead and as such vacuum is unable to clean them up  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi Tom,

just cleaned house in my mailbox and found this email that got buried. You were spot on with the prepared transactions, we had some hung Hibernate threads that were acting up.

Sorry for resurrecting this ages old thread, but wanted to say a big fat *THANKS*!

Cheers,
Tamas Kalman.

On Thu, Jul 6, 2017 at 11:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Tamás András Kálmán <hello@tamaskalman.com> writes:
> we have a PostgreSQL 9.3.4 database with multiple large tables, that keep
> growing.
> Looking at the pg_stat of  the front runner table that is currently about 1
> Gb  big, it seems, that stale row data is not marked as dead after updates,

Have you checked for uncommitted prepared transactions?
If "select * from pg_prepared_xacts" finds anything, that's
probably your problem.

                        regards, tom lane

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Copy entire schema A to a different schema B
Next
From:
Date:
Subject: Re: Connection string for Java to connect to PostgreSQL, usingclient certificates