Re: Avoid Wraparound Failures
От
Laurenz Albe
Тема
Re: Avoid Wraparound Failures
Дата
Msg-id
c3a1bd51686c32f399b7f23e48aec4820e8bad15.camel@cybertec.at
Ответ на
Список
Дерево обсуждения
Avoid Wraparound Failures Loles <lolesft@gmail.com>
Re: Avoid Wraparound Failures Ron <ronljohnsonjr@gmail.com>
Re: Avoid Wraparound Failures Laurenz Albe <laurenz.albe@cybertec.at>
Re: Avoid Wraparound Failures Ron <ronljohnsonjr@gmail.com>
Re: Avoid Wraparound Failures Laurenz Albe <laurenz.albe@cybertec.at>
Re: Avoid Wraparound Failures Loles <lolesft@gmail.com>
Re: Avoid Wraparound Failures Laurenz Albe <laurenz.albe@cybertec.at>
Re: Avoid Wraparound Failures Michael Banck <mbanck@gmx.net>
Re: Avoid Wraparound Failures Loles <lolesft@gmail.com>
Re: Avoid Wraparound Failures Peter Geoghegan <pg@bowt.ie>
Re: Avoid Wraparound Failures Loles <lolesft@gmail.com>
Re: Avoid Wraparound Failures Vijaykumar Jain <vijaykumarjain.github@gmail.com>
On Fri, 2022-03-25 at 23:45 -0500, Ron wrote: > > If you want to prevent that autovacuum run from happening while your system is > > busy (which normally also is no problem), you can trigger a manual VACUUM at > > a time of lower database activity. But make it a plain VACUUM, not a > > VACUUM (FREEZE) > > Why not VACUUM FREEZE? Because then you freeze *all* visible rows, not only those that are older than "vacuum_freeze_min_age". That will cause more pages to get dirtied, so there will be more writing I/O. And unless all these rows won't get modified in the forseeable future, that is a waste. "vacuum_freeze_min_age" is there for a reason: the expectation is that rows that have not been modified for 50 million transactions have better odds at not getting modified soon. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
В списке pgsql-admin по дате отправления
