Re: [GENERAL] transaction ID wraparound - should I use 'VACUUM' or 'VACUUM FULL' ?

2009-10-09 Thread Tom Lane
Alvaro Herrera writes: > Michal Szymanski wrote: >> In old version of Postgres we have to execute 'VACUUM FULL' to solve >> problem of transaction ID wraparound, do we need to execute 'VACUUM >> FULL' in Postgres 8.3 or 8.4 to avoid this problem? > No, plain VACUUM suffices. Just to clarify: pl

Re: [GENERAL] transaction ID wraparound - should I use 'VACUUM' or 'VACUUM FULL' ?

2009-10-09 Thread Alvaro Herrera
Michal Szymanski wrote: > Hi, > In old version of Postgres we have to execute 'VACUUM FULL' to solve > problem of transaction ID wraparound, do we need to execute 'VACUUM > FULL' in Postgres 8.3 or 8.4 to avoid this problem? No, plain VACUUM suffices. > How to check using SQL if transaction ID

[GENERAL] transaction ID wraparound - should I use 'VACUUM' or 'VACUUM FULL' ?

2009-10-09 Thread Michal Szymanski
Hi, In old version of Postgres we have to execute 'VACUUM FULL' to solve problem of transaction ID wraparound, do we need to execute 'VACUUM FULL' in Postgres 8.3 or 8.4 to avoid this problem? How to check using SQL if transaction ID is close to wraparound? Michal Szymanski http://blog.szymanski