From: | Simon Elbaz <elbazsimon9(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: PG16devel - vacuum_freeze_table_age seems not being taken into account |
Date: | 2023-03-03 11:25:07 |
Message-ID: | CAPOUM=e585GWHrhx4GxJnoOC3jrF4_Nks2hrNju-ORCtbxquAg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I ran vacuum without the freeze option as you can see below.
Simon
On Fri, Mar 3, 2023 at 12:01 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> On Fri, 3 Mar 2023 at 23:43, Simon Elbaz <elbazsimon9(at)gmail(dot)com> wrote:
> > hydrodb=# SELECT c.oid::regclass as table_name,
> > greatest(age(c.relfrozenxid),age(t.relfrozenxid)) as age
> > FROM pg_class c
> > LEFT JOIN pg_class t ON c.reltoastrelid = t.oid
> > WHERE c.relkind IN ('r', 'm') and c.relname='test';
> > table_name | age
> > ------------+-----
> > test | 51
> > (1 ligne)
> >
> > I expected it not to be processed by vacuum freeze.
> > However it has been entirely frozen.
>
> You may have missed the wording in the docs about the FREEZE option.
> "Specifying FREEZE is equivalent to performing VACUUM with the
> vacuum_freeze_min_age and vacuum_freeze_table_age parameters set to
> zero." [0]
>
> David
>
> [0] https://www.postgresql.org/docs/current/sql-vacuum.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Conner Bean | 2023-03-03 14:44:05 | Re: Dropping behavior for unique CONSTRAINTs |
Previous Message | David Rowley | 2023-03-03 11:01:44 | Re: PG16devel - vacuum_freeze_table_age seems not being taken into account |