Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Дата
Msg-id CAKFQuwbhDpOwB25TAEhcE9gTf8UK_aei98pae5Q0yBWLaO=KWQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Ron Johnson <ronljohnsonjr@gmail.com>)
Ответы Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Ron Johnson <ronljohnsonjr@gmail.com>)
Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum  (Scott Ribe <scott_ribe@elevated-dev.com>)
Список pgsql-admin
Дерево обсуждения
On Thu, May 9, 2024 at 7:21 AM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Thu, May 9, 2024 at 10:07 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thu, May 9, 2024 at 6:58 AM Ron Johnson <ronljohnsonjr@gmail.com> wrote:

I'm not wedded to the name RECREATE TABLE, but am wedded to the fact that VACUUM FULL is a horrible name for what it does.


I think there is general agreement here but your cure is arguably worse than the disease.

Why?  RECREATE TABLE says exactly what it does: recreates the table, and doesn't pretend to do something it doesn't do (vacuum the table).


That's distracting from the question at hand, which is whether and how to go about changing this, not whether the alternative naming is better than the existing one.  It isn't so much better that the pain of change seems worth it.  Mostly because it isn't like the universe simply gets reprogrammed to map the old onto the new, and having the old and new co-exist produces a burden.

David J.


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

Предыдущее
От: Ron Johnson
Дата:
Сообщение: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum
Следующее
От: Ron Johnson
Дата:
Сообщение: Re: Request for feature: VACUUM FULL updates pg_stat_all_tables.last_vacuum