Re: VACUUM and transaction ID wraparound
От | Martijn van Oosterhout |
---|---|
Тема | Re: VACUUM and transaction ID wraparound |
Дата | |
Msg-id | 20030517043419.GD3336@svana.org обсуждение исходный текст |
Ответ на | VACUUM and transaction ID wraparound ("Dean Gibson (DB Administrator)" <dba-sql@ultimeth.net>) |
Ответы |
Re: VACUUM and transaction ID wraparound
|
Список | pgsql-general |
On Fri, May 16, 2003 at 09:11:19PM -0700, Dean Gibson (DB Administrator) wrote: > The documentation says (Admin Guide, 8.2.3), "... each database-wide VACUUM automatically delivers a warning" if individualtables need VACUUMing to prevent transaction ID wraparound. > > But I thought a database-wide VACUUM automatically VACUUMed each table in the database (Ref Manual, 'VACUUM'), making (atleast to my way of thinking) VACUUMing an individual table unnecessary, and thus making the warning superfluous. > > Is there something here I don't understand? I beleive they are referring to the difference between VACUUM and VACUUM FULL. The former is faster and doesn't lock tables, but the latter is required to solve transaction wraparound. -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington
Вложения
В списке pgsql-general по дате отправления: