when issuing a "VACUUM ANALYZE {tablename}", the currently transaction wrap=
id is put into the logfile.
2006-10-22 07:04:50 LOG: transaction ID wrap limit is 2147484172, limited =
by database "postgres"
2006-10-22 07:04:56 LOG: transaction ID wrap limit is 2147484172, limited =
by database "postgres"
2006-10-22 07:05:02 LOG: transaction ID wrap limit is 2147484172, limited =
by database "postgres"
2006-10-22 07:05:14 LOG: transaction ID wrap limit is 2147484172, limited =
by database "postgres"
this can become annoying when one uses ANALYZE every few seconds for heavil=
y changing tables (session-tables) - the messages pile up in the server's l=
ogfiles.
i don't recall seen this behaviour in versions prior to 8.2b1
is this intended, and if yes, can it be turned off?
- thomas
