| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | jkoceniak(at)mediamath(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 17:13:24 |
| Message-ID: | CAKFQuwZ93Aaq-n9=V3R0W-Hz74mF1Cq42O9-nczus7d2jQoMLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jun 10, 2015 at 10:02 AM, <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
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | reiner peterke | 2015-06-10 17:25:54 | Re: 9.5 Import foreign schema error with user defined type in schema other than public. |
| Previous Message | David G. Johnston | 2015-06-10 17:10:36 | Re: BUG #13429: Update 0 rows for matching record |