| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Simon Elbaz <elbazsimon9(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:01:44 |
| Message-ID: | CAApHDvocc+Jaz9X2G0Uzxhbc5GN1Okdx3hg+wN1YFxm95H5wtQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Elbaz | 2023-03-03 11:25:07 | Re: PG16devel - vacuum_freeze_table_age seems not being taken into account |
| Previous Message | David Rowley | 2023-03-03 10:54:32 | Re: Dropping behavior for unique CONSTRAINTs |