| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: json datatype and table bloat? |
| Date: | 2013-10-29 20:51:54 |
| Message-ID: | 8632.1383079914@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John R Pierce <pierce(at)hogranch(dot)com> writes:
> On 10/29/2013 12:41 PM, Gregory Haase wrote:
>> db_name=# VACUUM FULL VERBOSE table_schema.table_name;
>> INFO: vacuuming "table_schema.table_name"
>> INFO: "table_name": found 2 removable, 29663 nonremovable row
>> versions in 1754 pages
>> DETAIL: 0 dead row versions cannot be removed yet.
>> CPU 0.07s/0.10u sec elapsed 0.30 sec.
> is there an old transaction pending? that 'masks' vacuum from touching
> any tuples newer than the start of that transaction.
If old transactions were the problem, vacuum would be reporting that
some-large-number of dead row versions couldn't be removed yet.
There doesn't seem to be anything obviously wrong here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Haase | 2013-10-29 21:01:13 | Re: json datatype and table bloat? |
| Previous Message | Gregory Haase | 2013-10-29 20:20:50 | Re: json datatype and table bloat? |