This is normal with postgresql 8.1 and above. With autovacuum turned on
in 8.1 (default), this reminder that you get every time you start up
your postgres server becomes merely informative, and no need to be of
concern. If your autovacuum is turned off, you need either to turn it on
(mostly recommended) or schedule a job to vacuum regularly to avoid
hitting the transaction wrap limit issue later on.


--
Husam
http://firstdba.googlepages.com


-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailtogsql-admin-owner@postgresql.org] On Behalf Of Abu Mushayeed
Sent: Friday, July 28, 2006 11:12 AM
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: [ADMIN] transaction ID wrap limit is 1073878048

Hello,

We just migrated our database to 8.1.3 from 7.4.12. I am noticing
messages
like

2006-07-16 03:30:22 PDTpostgrescansasLOG: transaction ID wrap limit is
1073878048, limited by database "webcalendar".

When we migrated, we had done a full vacuum of each database.

What is the cause of the problem. How can I fix this?


Thank you
Abu



---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
************************************************** ********************
This message contains confidential information intended only for the use of the addressee(s) named above and may contain information that is legally privileged. If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message immediately thereafter.

Thank you.

FADLD Tag
************************************************** ********************


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster