On Thu, Feb 25, 2010 at 6:15 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> Yeah, it's not very clear as it is.
>
> How about this:
>
> --- a/doc/src/sgml/recovery-config.sgml
> +++ b/doc/src/sgml/recovery-config.sgml
> @@ -193,7 +193,8 @@ restore_command = 'copy "C:\\server\\archivedir\\%f"
> "%p"'
> <listitem>
> <para>
> Specifies a connection string to be used for the standby server
> - to connect with the primary. This string is in the same format as
> + to connect with the primary. This string is in the format
> + accepted by the libpq <function>PQconnectdb</function> function,
> described in <xref linkend="libpq-connect">. If any option is
> unspecified in this string, then the corresponding environment
> variable (see <xref linkend="libpq-envars">) is checked. If the
The following description in the document about PQconnectdb() doesn't fit
primary_conninfo because of restriction of readRecoveryCommandFile().
---------------
To write an empty value, or a value containing spaces,
surround it with single quotes, e.g., keyword = 'a value'. Single quotes
and backslashes within the value must be escaped with a backslash,
i.e., \' and \\.
---------------
So I'd like to copy and paste the description about conninfo except the
above. Thought? Here is the patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center