Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1baIqd-0006qQ-B0 for pgsql-docs@arkaria.postgresql.org; Thu, 18 Aug 2016 08:38:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1baIqc-0001wC-6U for pgsql-docs@arkaria.postgresql.org; Thu, 18 Aug 2016 08:38:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1baIqF-0001YE-Gd for pgsql-docs@postgresql.org; Thu, 18 Aug 2016 08:38:23 +0000 Received: from mail-lf0-x229.google.com ([2a00:1450:4010:c07::229]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1baIqC-0001W8-8K for pgsql-docs@postgresql.org; Thu, 18 Aug 2016 08:38:22 +0000 Received: by mail-lf0-x229.google.com with SMTP id b199so7232584lfe.0 for ; Thu, 18 Aug 2016 01:38:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version; bh=mJWuxHmltfDQBI5hNbRRjlSAoWTLD998DzuGm+PtyqU=; b=kLO79t+Of3T8FwIhHmFTJTC6dNTvGP6UDS9s6aY3LRuKFkiAkJy5NWt6AqcQVPN1V0 /iGUOKZP7AIvp89PL502xBF+WJROEwM5JiTDx6VhQEzqmkyQ96LTKVOgZnc/yhmCkQ5L zVqVPDs++gV8nwiGHuMXBkSCrq0ZzTqN2Kh2BjuSiWXuL/xDlWs3ILzyy/1z/AbKbygT WvZs/UXyisBjRSFDbaoolfHMgltqB8supHlstycyjvghmtYuYv1io9pFWlw7xuZ0T/ex bS31Tj2xJvVZ/8xvf1UOJObKGilTyXX3TE16i47+3Tf5huwlLw8ABT92/iE5xTnIM05g 1dMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=mJWuxHmltfDQBI5hNbRRjlSAoWTLD998DzuGm+PtyqU=; b=XMdsCzDgrjDMDGSPWtRc9o1pZ0FpCD+PZFiWGuby8/HL8kFqWGzx7S8tPufvSkPm5C XJJpOXDDWjlPeHl1pbHpiK42KyYX/wF/L3qcXCJ0JFIgAWLsEzAJuSSuIdHB7a37zDXd c6obCJouXTMndSxn4h8vhgbXQ/P1e098NFGQCgNRv9snENSrJU3RZbiJ4sbyW+eRezlE b/nqBj/3HYnKKwlgmGIU4lo0OXtU0l66MOglM4ZJB6vbR1d3ATSsNJ/H+UlTjq9Ubo2m 8tAWbOSPp0Vd9bgwXpQ+HBaVSFr52MLyY996cp/GE1e8bZ1COjJ8+jZj1U9gWmKeXrIl sVIA== X-Gm-Message-State: AEkoouvQNsKNTeY1OflrokWXM9BrONYNaGp4iPtDENNKd6m/yL4CrtdX/+7sHfqVOjAXPg== X-Received: by 10.46.32.5 with SMTP id g5mr285207ljg.53.1471509497289; Thu, 18 Aug 2016 01:38:17 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.92]) by smtp.gmail.com with ESMTPSA id m62sm160118lfe.44.2016.08.18.01.38.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Aug 2016 01:38:16 -0700 (PDT) To: "pgsql-docs@postgresql.org" From: Alexander Law Subject: Incorrect 'literal' tags Message-ID: Date: Thu, 18 Aug 2016 11:38:15 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------6655B800054D25686C641827" X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org This is a multi-part message in MIME format. --------------6655B800054D25686C641827 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, While translating docs I encountered an inconsistency with the literal/replaceable Docbook tags. I believe that the 'replaceable' tag should be used for keywords that intended to be replaced with some values, but 'literal' is for literal usage. But there are some places in the docs where 'literal' is used for replaceable values. Patch attached. Best regards, Alexander --------------6655B800054D25686C641827 Content-Type: text/x-patch; name="literal-replaceable.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="literal-replaceable.patch" diff --git a/doc/src/sgml/pgstandby.sgml b/doc/src/sgml/pgstandby.sgml index fb3f32e..80c6f60 100644 --- a/doc/src/sgml/pgstandby.sgml +++ b/doc/src/sgml/pgstandby.sgml @@ -363,7 +363,7 @@ recovery_end_command = 'del C:\pgsql.trigger.5442' The copy command on Windows sets the final file size before the file is completely copied, which would ordinarily confuse pg_standby. Therefore - pg_standby waits sleeptime + pg_standby waits sleeptime seconds once it sees the proper file size. GNUWin32's cp sets the file size only after the file copy is complete. diff --git a/doc/src/sgml/ref/pg_xlogdump.sgml b/doc/src/sgml/ref/pg_xlogdump.sgml index 296f1ac..177caab 100644 --- a/doc/src/sgml/ref/pg_xlogdump.sgml +++ b/doc/src/sgml/ref/pg_xlogdump.sgml @@ -153,7 +153,7 @@ PostgreSQL documentation Timeline from which to read log records. The default is to use the - value in startseg, if that is specified; otherwise, the + value in startseg, if that is specified; otherwise, the default is 1. diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index f58da35..285608d 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -433,7 +433,7 @@ pgbench options dbname sec - Show progress report every sec seconds. The report + Show progress report every sec seconds. The report includes the time since the beginning of the run, the tps since the last report, and the transaction latency average and standard deviation since the last report. Under throttling (