Thanks, applied. ---------------------------------------------------------------------------
Fujii Masao wrote: > > The following bug has been logged online: > > Bug reference: 3486 > Logged by: Fujii Masao > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.3 > Operating system: RHEL4 > Description: doc bug - Preventing transaction ID wraparound failures > Details: > > According to "varsup.c - GetNewTransactionId()", the error message in > transaction ID wraparound failures > is different from the one in the document. > > > *** ./doc/src/sgml/maintenance.sgml.orig 2007-07-26 10:44:19.000000000 > +0900 > --- ./doc/src/sgml/maintenance.sgml 2007-07-26 10:45:11.000000000 +0900 > *************** > *** 447,453 **** > until wraparound: > > <programlisting> > ! ERROR: database is shut down to avoid wraparound data loss in database > "mydb" > HINT: Stop the postmaster and use a standalone backend to VACUUM in > "mydb". > </programlisting> > > --- 447,453 ---- > until wraparound: > > <programlisting> > ! ERROR: database is not accepting commands to avoid wraparound data loss > in database "mydb" > HINT: Stop the postmaster and use a standalone backend to VACUUM in > "mydb". > </programlisting> > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
