Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1esCn4-0005V8-SZ for pgsql-docs@arkaria.postgresql.org; Sat, 03 Mar 2018 19:25:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1esCn3-0002Xj-HU for pgsql-docs@arkaria.postgresql.org; Sat, 03 Mar 2018 19:25:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1esCn3-0002Xa-1y for pgsql-docs@lists.postgresql.org; Sat, 03 Mar 2018 19:25:53 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1esCmy-0006qv-HG for pgsql-docs@lists.postgresql.org; Sat, 03 Mar 2018 19:25:51 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 28890209F3; Sat, 3 Mar 2018 14:25:47 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Sat, 03 Mar 2018 14:25:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=SBWtyw XN0LRYqlUHQQbNDI2P9TRcqeJzLkZ6YmNOY3A=; b=NGVBy5BWRwmu+PO0nFHRK6 DE2jQ/wmMAFbpIi8drL5Z0NUqLlaAKppPAC/qEt1ahMyyw0CqMWWOjxRC6yFqEJ1 jc1RJcrqZ12Ej2YtK30ur4JcWYgcIlAMq6gCg0AR8/LD4ajJnBGG0P3HBxTWl2tD e6WxT+r6xmnNAsW3iBoB4OlJ6TKDUit3Y5az/QxIa5EqIJ99fPoRum/QuqHpWPhU kDjxnr2MjNZ8KyEBgfOCIOh8Eh9GnAQYHNpoBzzGagf+1Kp0C+ITJ7vtr3/7hG+P Gls2KwGamDfcLYfBT2PMCpDgkMC43NN1zAlMah63jwOre2Vj/8BjaB+iFApbHfFw == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id AD8CF7E4BB; Sat, 3 Mar 2018 14:25:46 -0500 (EST) Subject: Re: Fix links to pg_stat_replication and definition of checkpoint_warning GUC To: Maksim Milyutin , pgsql-docs@lists.postgresql.org References: <242ec876-177d-66f5-144c-48ee217e99a9@gmail.com> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <06744008-626e-a634-e221-7f988c93ef7b@2ndquadrant.com> Date: Sat, 3 Mar 2018 14:25:46 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <242ec876-177d-66f5-144c-48ee217e99a9@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/19/18 05:25, Maksim Milyutin wrote: > I have noticed that in documentation for PG versions before 11devel some > *pg_stat_replication/* /links refer to *collected statistic views* table > instead of itself definition. Fixes for version 10.2 are gathered in > fix_pg_stat_replication_links_doc.patch This was due to a reorganization of the documentation in 9.5, so the links became outdated. Fixed. > Also I am confused by the definition of *checkpoint_warning* parameter, > namely the phrase "caused by the filling of checkpoint segment files". I > think the word "checkpoint" is unnecessary here. I tried to rephrase > this definition in fix_checkpoint_warning_definition_doc.patch. This was more appropriate when the related parameter was called checkpoint_segments, but now it indeed seems confusing. Also fixed. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services