From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: vacuum on table with all rows frozen |
Date: | 2017-04-01 16:34:17 |
Message-ID: | b4a0a898-3fad-2a97-0e9b-44963b7193eb@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/01/2017 09:09 AM, Tom DalPozzo wrote:
> Hi,
> let's suppose I have a table which after beign populated with only
> INSERTs, doesn't receive no more writing queries (neither insert or
> update or delete). Only reading queries.
> Once all table rows get frozen by (auto)vacuum, will a next (auto)vacuum
> scan that table for any reason or does it understand that it would be
> useless (as no more rows to mark as forzen and no dead tuples) ?
What version of Postgres?
Don't vacuum all-frozen pages.:
That made it into 9.6:
https://www.postgresql.org/docs/9.6/static/release-9-6.html
E.3.3.1.6. VACUUM
Avoid re-vacuuming pages containing only frozen tuples (Masahiko Sawada,
Robert Haas, Andres Freund)
> As I will have hunderds of big tables like that, I want to be sure that
> the vacuum process doesn't waste time.
> Regards
> Pupillo
>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom DalPozzo | 2017-04-01 16:50:25 | Re: vacuum on table with all rows frozen |
Previous Message | Tom DalPozzo | 2017-04-01 16:09:37 | vacuum on table with all rows frozen |