Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6F677632562 for ; Fri, 12 Feb 2010 12:15:35 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 81759-06 for ; Fri, 12 Feb 2010 16:15:25 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f212.google.com (mail-bw0-f212.google.com [209.85.218.212]) by mail.postgresql.org (Postfix) with ESMTP id A9202632F50 for ; Fri, 12 Feb 2010 12:15:24 -0400 (AST) Received: by bwz4 with SMTP id 4so2221368bwz.22 for ; Fri, 12 Feb 2010 08:15:23 -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 :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=sdDitdjIcucfpEELATy+dWOU9BmN4ceqYRZGpVdkUPc=; b=bUaShRqpCxjzGlMPXCRwqp740OAfmQzeX2YwZ8payADs3nuVaqjuF/WWanaQUGTdK+ GoH3GWWXeTCkH2La+dlgAOw7AR7vFTtu4pm0YG1WagM+ueuzE96zb+5E7Tmi0US94t45 UjLno6KiVpn7jv7tQqMyALBSPNIoYFN805s00= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=dUaNhYzBN/Pk3Xaif9yAouikY2/Z3dc4zlDYo2tjF9DUSfPQ+Wl6OQY7W4X54tMj5a oJciAU8/2m9qxqDVmlCtXzSHqOt/Rvv6NUMrsSyCHSkU0pfrOhE77pZnfAHTd71kAzgm jcyPeX3YaxjCv9jJZ3jHNO5njzE5dvsJ707Is= MIME-Version: 1.0 Received: by 10.103.35.5 with SMTP id n5mr1052868muj.132.1265991323176; Fri, 12 Feb 2010 08:15:23 -0800 (PST) In-Reply-To: <3f0b79eb1002111757y3d11102n7fdfcee8f332f6d4@mail.gmail.com> References: <3f0b79eb1002111757y3d11102n7fdfcee8f332f6d4@mail.gmail.com> From: Thom Brown Date: Fri, 12 Feb 2010 16:15:03 +0000 Message-ID: Subject: Re: Confusing link in streaming replication section To: Fujii Masao 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=-0.838 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FS_REPLICA=1.041, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 201002/6 X-Sequence-Number: 5322 On 12 February 2010 01:57, Fujii Masao wrote: > 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.h= tml) >> and under the description of primary_conninfo, there's a link to >> section 30.1 (http://developer.postgresql.org/pgdocs/postgres/libpq-conn= ect.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 committ= ed. > 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 equ= al > 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 quote= s > 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. > ----------- Hmmm... well that last sentence refers to parameter key words which won't appear on the SR page unless you copy and paste all that information too. I think the problem I have with there being a link to the libpq control functions page is that the context of the settings isn't the same, meaning the text on that page is specifically targetting people looking for libpq info, rather than providing more generic information which may be better placed in an appendix or something similar. May I suggest a page on connection paramaters/connection strings which can be referenced by multiple locations? Otherwise I can imagine the same information being presented a number of times throughout the documentation. Thanks Thom