Re: BUG #13426: table bloat - dead rows not removed after vacuum - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13426: table bloat - dead rows not removed after vacuum
Date
Msg-id CAKFQuwZ93Aaq-n9=V3R0W-Hz74mF1Cq42O9-nczus7d2jQoMLQ@mail.gmail.com
Whole thread Raw
In response to BUG #13426: table bloat - dead rows not removed after vacuum  (jkoceniak@mediamath.com)
Responses Re: BUG #13426: table bloat - dead rows not removed after vacuum
List pgsql-bugs
On Wed, Jun 10, 2015 at 10:02 AM, <jkoceniak@mediamath.com> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      13426
> Logged by:          Jamie
> Email address:      jkoceniak@mediamath.com
> PostgreSQL version: 9.1.14
> Operating system:    x86_64-unknown-linux-gnu debian
> Description:
>
> I have a table that is growing out of control.
>
> After doing a vacuum, the dead rows still remain. Why can't they be
> removed?
>
> DETAIL:  214063622 dead row versions cannot be removed yet.
>

=E2=80=8BOne possibility is that =E2=80=8B
you have a long-running transaction holding up cleanup.

Viewing "pg_stat_activity" will be informative.

=E2=80=8BDavid J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #13429: Update 0 rows for matching record
Next
From: reiner peterke
Date:
Subject: Re: 9.5 Import foreign schema error with user defined type in schema other than public.