RE: visibility map corruption

Поиск
Список
Период
Сортировка
От Floris Van Nee
Тема RE: visibility map corruption
Дата
Msg-id bbea09c93b76447aa0b95d89f7beac2d@opammb0562.comp.optiver.com
обсуждение исходный текст
Ответ на Re: visibility map corruption  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: visibility map corruption
Список pgsql-hackers
> 
> I wonder if it's related to this issue:
> 
> https://www.postgresql.org/message-
> id/20210423234256.hwopuftipdmp3okf@alap3.anarazel.de
> 
> Have you increased autovacuum_freeze_max_age from its default? This
> already sounds like the kind of database where that would make sense.
> 

autovacuum_freeze_max_age is increased in our setup indeed (it is set to 500M). However, we do regularly run manual
VACUUM(FREEZE) on individual tables in  the database, including this one. A lot of tables in the database follow an
INSERT-onlypattern and since it's not running v13 yet, this meant that these tables would only rarely be touched by
autovacuum.Autovacuum would sometimes kick in on some of these tables at the same time at unfortunate moments.
Thereforewe have some regular job running that VACUUM (FREEZE)s tables with a xact age higher than a (low, 10M)
thresholdourselves.
 


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

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: "debug_invalidate_system_caches_always" is too long
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Disable WAL logging to speed up data loading