[DOCS] recovery configuration parameters
Hi, While the server configuration parameters are listed in the index page, why not the recovery ones? It's very inconvenient to be unable to reach the document of them immediately when setting up the standby server. How about listing the recovery configuration parameters in the index page? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] code example wrapping
Erik Rijkers wrote: > On Mon, April 5, 2010 19:29, Peter Eisentraut wrote: > > On mån, 2010-04-05 at 18:30 +0200, Erik Rijkers wrote: > >> On Mon, April 5, 2010 18:18, Tom Lane wrote: > >> > "Erik Rijkers" writes: > >> > > >> >> I would like to reformat (only) those cases so that the text is > >> >> completely readable on the > > Here is plpgsql.sgml with reformatted code-examples for pdf readability > (mainly split long lines; also fixed an concat error in one example). > > I've checked A4+US pdf's and html with these changes - they look OK, I think. Just applied it. I checked the HTML output and it looks good. I couldn't generate the PDF now; it died like this: $ make postgres-A4.pdf openjade -D . -D /pgsql/source/900orig/doc/src/sgml -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d /pgsql/source/900orig/doc/src/sgml/stylesheet.dsl -t tex -V tex-backend -i output-print -i include-index -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf /pgsql/source/900orig/doc/src/sgml/postgres.sgml pdfjadetex postgres-A4.tex-pdf This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) restricted \write18 enabled. ---! /var/lib/texmf/web2c/pdftex/pdfjadetex.fmt doesn't match pdftex.pool (Fatal format file error; I'm stymied) make: *** [postgres-A4.pdf] Error 1 rm postgres-A4.tex-pdf I don't know what's going on but I bet it has to do with something I upgraded on this machine. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] code example wrapping
Alvaro Herrera writes: > Just applied it. I checked the HTML output and it looks good. I > couldn't generate the PDF now; it died like this: > ---! /var/lib/texmf/web2c/pdftex/pdfjadetex.fmt doesn't match pdftex.pool > (Fatal format file error; I'm stymied) That's an installation problem... I can still build the .pdf, but only if I have a jadetex.cfg with a modified FlowObjectSetup macro as per http://archives.postgresql.org/pgsql-docs/2010-04/msg00022.php I'm not entirely sure that that macro is right, but we really are going to need to do something about it soon, if we'd like people to be able to build the beta docs. Anybody have any comments? regards, tom lane -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] recovery configuration parameters
Fujii Masao wrote: > While the server configuration parameters are listed in > the index page, why not the recovery ones? It's very > inconvenient to be unable to reach the document of them > immediately when setting up the standby server. > > How about listing the recovery configuration parameters > in the index page? Agreed. This patch should do it. It lists them as "XXX recovery parameter", e.g: restore_command recovery parameter, Archive recovery settings similar to the way GUCs are listed as "XXX configuration parameter". PS. I just noticed that the links in the index for GUCs take you to the section in the manual, not directly to the parameter. For example, when you click on the index term for "max_connections", it takes you to section "18.3.1 Connection Settings" (the link points to http://developer.postgresql.org/pgdocs/postgres/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS), which begins with listen_addresses. max_connections is there a few paragraphs down, but I would've expected the link to point directly to description of the parameter. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] recovery configuration parameters
On Wed, Apr 28, 2010 at 4:52 AM, Heikki Linnakangas wrote: > Fujii Masao wrote: >> While the server configuration parameters are listed in >> the index page, why not the recovery ones? It's very >> inconvenient to be unable to reach the document of them >> immediately when setting up the standby server. >> >> How about listing the recovery configuration parameters >> in the index page? > > Agreed. This patch should do it. Which patch? > PS. I just noticed that the links in the index for GUCs take you to the > section in the manual, not directly to the parameter. For example, when > you click on the index term for "max_connections", it takes you to > section "18.3.1 Connection Settings" (the link points to > http://developer.postgresql.org/pgdocs/postgres/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS), > which begins with listen_addresses. max_connections is there a few > paragraphs down, but I would've expected the link to point directly to > description of the parameter. I think that such a direct link is useful, but I'm not sure how. Though I added the "zone" attribute into the "indexterm" tag for "max_connections" as a trial, I was not able to get the expected result. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] recovery configuration parameters
Fujii Masao wrote: > On Wed, Apr 28, 2010 at 4:52 AM, Heikki Linnakangas > wrote: >> Fujii Masao wrote: >>> While the server configuration parameters are listed in >>> the index page, why not the recovery ones? It's very >>> inconvenient to be unable to reach the document of them >>> immediately when setting up the standby server. >>> >>> How about listing the recovery configuration parameters >>> in the index page? >> Agreed. This patch should do it. > > Which patch? Ah, crap. This one. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml index 3aff445..439db3f 100644 --- a/doc/src/sgml/recovery-config.sgml +++ b/doc/src/sgml/recovery-config.sgml @@ -36,6 +36,9 @@ restore_command (string) + +restore_command recovery parameter + The shell command to execute to retrieve an archived segment of @@ -72,6 +75,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows restartpoint_command (string) + +restartpoint_command recovery parameter + This parameter specifies a shell command that will be executed at @@ -98,6 +104,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows recovery_end_command (string) + +recovery_end_command recovery parameter + This parameter specifies a shell command that will be executed once only @@ -129,6 +138,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows recovery_target_time (timestamp) + +recovery_target_time recovery parameter + This parameter specifies the time stamp up to which recovery @@ -144,6 +156,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows recovery_target_xid (string) + +recovery_target_xid recovery parameter + This parameter specifies the transaction ID up to which recovery @@ -166,6 +181,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows recovery_target_inclusive (boolean) + +recovery_target_inclusive recovery parameter + Specifies whether we stop just after the specified recovery target @@ -185,6 +203,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows recovery_target_timeline (string) + +recovery_target_timeline recovery parameter + Specifies recovering into a particular timeline. The default is @@ -207,6 +228,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows standby_mode (boolean) + + standby_mode recovery parameter + Specifies whether to start the PostgreSQL server as @@ -221,6 +245,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows primary_conninfo (string) + + primary_conninfo recovery parameter + Specifies a connection string to be used for the standby server @@ -254,6 +281,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows trigger_file (string) + + trigger_file recovery parameter + Specifies a trigger file whose presence ends recovery in the -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
