Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id D9F466323A4 for ; Thu, 11 Feb 2010 21:58:05 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 87595-07 for ; Fri, 12 Feb 2010 01:57:38 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-yx0-f186.google.com (mail-yx0-f186.google.com [209.85.210.186]) by mail.postgresql.org (Postfix) with ESMTP id 40CC8632D64 for ; Thu, 11 Feb 2010 21:57:55 -0400 (AST) Received: by yxe16 with SMTP id 16so1733066yxe.1 for ; Thu, 11 Feb 2010 17:57:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cl+RugJYx9snMAx4HMQipl5mPKmhqahzSmvYKxFCRHA=; b=XBzqP7r8yDKdhEY0OWC2bWd/1DQsZoEW0FfzkAaLa7n4MDwj8QRwzfZJUayEXjoPFv gmdOETDHRTZlBJLKSB8PvXUFz28OOwS5YcT5Q1aZz91W26qahAnohae4jrub3nFPHqb/ qO12wTepdjJmHsN5Hv1z6q27TqZbHwNTr5LAg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SnrTnkagGyUSISFX+z6hoYh65iJTdX7iRx6M5ivKz7HtrzTkqqJLW69ckn9yKOjrz9 ogim1FguhnLjgsCfC6tzjn520QTwJzZ2EYXkTAPxtJqT1XkKRFnw07CLiRyD1VkNNTWI xtbtcngZ6Q4xx2NDU3xBHZyCVu55xq3YhEtzw= MIME-Version: 1.0 Received: by 10.101.138.20 with SMTP id q20mr1067018ann.160.1265939873558; Thu, 11 Feb 2010 17:57:53 -0800 (PST) In-Reply-To: References: Date: Fri, 12 Feb 2010 10:57:53 +0900 Message-ID: <3f0b79eb1002111757y3d11102n7fdfcee8f332f6d4@mail.gmail.com> Subject: Re: Confusing link in streaming replication section From: Fujii Masao To: Thom Brown Cc: pgsql-docs@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.09 tagged_above=-10 required=5 tests=AWL=-0.252, BAYES_00=-2.599, FS_REPLICA=1.041, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 201002/5 X-Sequence-Number: 5321 On Thu, Feb 11, 2010 at 7:43 AM, Thom Brown wrote: > I'm looking at the latest docs for PostgreSQL 9.0 > (http://developer.postgresql.org/pgdocs/postgres/streaming-replication.ht= ml) > and under the description of primary_conninfo, there's a link to > section 30.1 (http://developer.postgresql.org/pgdocs/postgres/libpq-conne= ct.html) > which is supposed to describe the string format. =A0Having looked at > that page, however, it's not crystal clear what is meant by this > string format. =A0One can only assume it's referring to the > PQconnectdbParams section and the keywords that can be used for it, > which would also apply to a connection string, but there's no mention > of a "format" on that page. Thanks for the report! Though at first PQconnectdb() had been linked by the SR doc, instead PQconnectdbParams() seems to have been linked wrongly when it was committed= . How about changing the link so as to point to PQconnectdb() again? Or copy-pasting the following description from PQconnectdb() to the SR doc? ----------- The passed string can be empty to use all default parameters, or it can contain one or more parameter settings separated by whitespace. Each parameter setting is in the form keyword =3D value. Spaces around the equal sign are optional. To write an empty value, or a value containing spaces, surround it with single quotes, e.g., keyword =3D 'a value'. Single quotes and backslashes within the value must be escaped with a backslash, i.e., \' and \\. The currently recognized parameter key words are the same as above. ----------- Regards, --=20 Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center