Re: VACUUM FULL doesn't reduce table size

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>, pinker <pinker(at)onet(dot)eu>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: VACUUM FULL doesn't reduce table size
Date: 2015-03-09 15:57:17
Message-ID: 54FDC2DD.3010103@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/09/2015 08:49 AM, Kevin Grittner wrote:
> pinker <pinker(at)onet(dot)eu> wrote:
>
>> INFO: vacuuming "my_table"
>> INFO: "my_table": found 0 removable, 3043947 nonremovable row versions in 37580 pages
>> DETAIL: 0 dead row versions cannot be removed yet.
>
> So there are no longer any dead rows being left behind, right?
>
> Why are we still discussing this? Do you have some other question?

Well from the original post:

"I have deleted a large number of records from my_table, which
originally had 288 MB. Then I ran vacuum full to make the table size
smaller. After this operation size of the table remains the same,
despite of the fact that table contains now only 241 rows and after
rewriting it in classic way: CREATE TABLE new_table AS SELECT * FROM
old_table - new_table size is 24kB. "

So I think the question remains how is 241 rows = 3043947 nonremovable
row versions? And that number is an increase from the original number
which was 2989662 nonremovable row versions.

>
> --
> Kevin Grittner
> EDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message pinker 2015-03-09 16:05:07 Re: VACUUM FULL doesn't reduce table size
Previous Message Adrian Klaver 2015-03-09 15:54:15 Re: VACUUM FULL doesn't reduce table size