Re: PG16devel - vacuum_freeze_table_age seems not being taken into account

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: PG16devel - vacuum_freeze_table_age seems not being taken into account
Дата
Msg-id CAApHDvocc+Jaz9X2G0Uzxhbc5GN1Okdx3hg+wN1YFxm95H5wtQ@mail.gmail.com
обсуждение исходный текст
Ответ на PG16devel - vacuum_freeze_table_age seems not being taken into account  (Simon Elbaz <elbazsimon9@gmail.com>)
Ответы Re: PG16devel - vacuum_freeze_table_age seems not being taken into account  (Simon Elbaz <elbazsimon9@gmail.com>)
Список pgsql-general
On Fri, 3 Mar 2023 at 23:43, Simon Elbaz <elbazsimon9@gmail.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



В списке pgsql-general по дате отправления:

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Dropping behavior for unique CONSTRAINTs
Следующее
От: Simon Elbaz
Дата:
Сообщение: Re: PG16devel - vacuum_freeze_table_age seems not being taken into account