BUG #3486: doc bug - Preventing transaction ID wraparound failures

On Jul 26, 2007, at 4:09 AM, Fujii Masao wrote:

The following bug has been logged online:

Bug reference: 3486
Logged by: Fujii Masao
Email address: fujii.masao@oss.ntt.co.jp
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>

Is there any way we could extend the po system to allow for calling
out actual error messages from code into the docs? I see that the .po
files call out source code files and locations...

As an alternative, I could probably come up with something that would
allow for putting error message examples in comments in the source
code so at least if someone's changing something they can just change
it in one place.
--
Decibel!, aka Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

Thanks, applied.

---------------------------------------------------------------------------

Fujii Masao wrote:

The following bug has been logged online:

Bug reference: 3486
Logged by: Fujii Masao
Email address: fujii.masao@oss.ntt.co.jp
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 <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +