Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 4E0E4633B5A for ; Tue, 27 Apr 2010 23:16:56 -0300 (ADT) 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 80529-09 for ; Wed, 28 Apr 2010 02:16:44 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f204.google.com (mail-yw0-f204.google.com [209.85.211.204]) by mail.postgresql.org (Postfix) with ESMTP id D308C633B3C for ; Tue, 27 Apr 2010 23:16:45 -0300 (ADT) Received: by ywh42 with SMTP id 42so6659612ywh.15 for ; Tue, 27 Apr 2010 19:16:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=02QVuSWlFc1ZA8hL2JyIhaV4IIH9O6gP63iheGY0k7s=; b=RG2S4VLfxseYzmI2gPrhyXT4/+jHYToY+qwY8ki8KhwFkKPYUEyWOIKq+2WLaAfSdX AfInvozMuE0qInbsde2kH9IJktRjwjX3ztRXxGVj5q84cifaPPkTWFisqr5F9fJWqEo7 ZUavnsI5csffHileYdfYd2xXsF/QoOIiiFq8M= 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; b=gaB66SbSrtYH1t9nPVRP4T03uTvhcfcdpnAkmIa8VqlipYlykqCPNFBEcCsYJHbJu4 jFdvq4x56MPIGGmiDb9e+ckxf84TrGT0/BpsOJMhRguXKTdT5oj3tN9UMzZzhpLThBp9 zug6OoFJ2KasBPa94R0HTigu2qekZ57y/MWDA= MIME-Version: 1.0 Received: by 10.101.63.13 with SMTP id q13mr2259851ank.146.1272421003831; Tue, 27 Apr 2010 19:16:43 -0700 (PDT) Received: by 10.100.142.12 with HTTP; Tue, 27 Apr 2010 19:16:43 -0700 (PDT) In-Reply-To: <4BD7407E.5050507@enterprisedb.com> References: <4BD7407E.5050507@enterprisedb.com> Date: Wed, 28 Apr 2010 11:16:43 +0900 Message-ID: Subject: Re: recovery configuration parameters From: Fujii Masao To: heikki.linnakangas@enterprisedb.com Cc: pgsql-docs@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.889 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201004/89 X-Sequence-Number: 5488 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