Re: [GENERAL] Modified rows are not marked as dead and as such vacuum is unable to clean them up

From: Tamás András Kálmán <hello(at)tamaskalman(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Modified rows are not marked as dead and as such vacuum is unable to clean them up
Date: 2019-02-21 21:07:59
Message-ID: CAAV1k2fJT9U3a55kQWmVR_8Yvn88DVGfdSZT98nooNcthe06CQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> =?UTF-8?B?VGFtw6FzIEFuZHLDoXMgS8OhbG3DoW4=?= <hello(at)tamaskalman(dot)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
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message s400t 2019-02-21 22:24:19 Re: Connection string for Java to connect to PostgreSQL, using client certificates
Previous Message Adrian Klaver 2019-02-21 20:23:10 Re: Copy entire schema A to a different schema B