Re: BUG #13426: table bloat - dead rows not removed after vacuum

From: Jamie Koceniak <jkoceniak(at)mediamath(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13426: table bloat - dead rows not removed after vacuum
Date: 2015-06-10 21:39:45
Message-ID: 84CE67AB46ACDA41B18094177DD0853D3A8AC2@ORD2MBX04C.mex05.mlsrvr.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi David,

No long running queries are in pg_stat_activity.
I was also able to take this same table and import onto another server, perform millions of deletes and inserts to recreate the problem.
The ‘Vacuum tablename‘ command is not removing dead row versions.

Thanks for the quick reply,
Jamie

From: David G. Johnston [mailto:david(dot)g(dot)johnston(at)gmail(dot)com]
Sent: Wednesday, June 10, 2015 10:13 AM
To: Jamie Koceniak
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #13426: table bloat - dead rows not removed after vacuum

On Wed, Jun 10, 2015 at 10:02 AM, <jkoceniak(at)mediamath(dot)com<mailto:jkoceniak(at)mediamath(dot)com>> wrote:
The following bug has been logged on the website:

Bug reference: 13426
Logged by: Jamie
Email address: jkoceniak(at)mediamath(dot)com<mailto:jkoceniak(at)mediamath(dot)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.

​One possibility is that ​
you have a long-running transaction holding up cleanup.

Viewing "pg_stat_activity" will be informative.

​David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2015-06-10 22:16:42 Re: BUG #13426: table bloat - dead rows not removed after vacuum
Previous Message David Fetter 2015-06-10 19:03:52 Re: 9.5 Import foreign schema error with user defined type in schema other than public.