Re: autovacuum next steps
От | Chris Browne |
---|---|
Тема | Re: autovacuum next steps |
Дата | |
Msg-id | 60hctl7k9k.fsf@dba2.int.libertyrms.com обсуждение исходный текст |
Ответ на | autovacuum next steps (Alvaro Herrera <alvherre@commandprompt.com>) |
Список | pgsql-hackers |
alvherre@commandprompt.com (Alvaro Herrera) writes: > When there is a single worker processing a database, it does not recheck > pgstat data after each table. This is to prevent a high-update-rate > table from starving the vacuuming of other databases. This case is important; I don't think that having multiple workers fully alleviates the problem condition. Pointedly, you need to have a way of picking up tables often enough to avoid the XID rollover problem. That may simply require that on some periodic basis, a query is run to queue up tables that are getting close to having an "XID problem." -- (reverse (concatenate 'string "ofni.secnanifxunil" "@" "enworbbc")) http://linuxfinances.info/info/finances.html Rules of the Evil Overlord #189. "I will never tell the hero "Yes I was the one who did it, but you'll never be able to prove it to that incompetent old fool." Chances are, that incompetent old fool is standing behind the curtain." <http://www.eviloverlord.com/>
В списке pgsql-hackers по дате отправления: