Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hfUNz-00011D-Vh for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jun 2019 19:12:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hfUNy-0004Gn-Hl for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jun 2019 19:12:14 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hfUNy-0004Gg-8u for pgsql-hackers@lists.postgresql.org; Mon, 24 Jun 2019 19:12:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hfUNw-0005dI-6w for pgsql-hackers@postgresql.org; Mon, 24 Jun 2019 19:12:13 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x5OJC9Na015033; Mon, 24 Jun 2019 15:12:09 -0400 From: Tom Lane To: Stephen Frost cc: Robert Haas , Ian Barwick , Amit Kapila , "pgsql-hackers@postgresql.org" Subject: Re: [PATCH] Stop ALTER SYSTEM from making bad assumptions In-reply-to: <20190624185647.GW2480@tamriel.snowman.net> References: <20190614160835.GF2480@tamriel.snowman.net> <20190616171610.GO2480@tamriel.snowman.net> <27dc9f8d-8d8f-9dd1-0494-5d8bd2f49a45@2ndquadrant.com> <20372.1561134638@sss.pgh.pa.us> <20190621164028.GO2480@tamriel.snowman.net> <21353.1561136112@sss.pgh.pa.us> <20190624185647.GW2480@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Mon, 24 Jun 2019 14:56:47 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15031.1561403529.1@sss.pgh.pa.us> Date: Mon, 24 Jun 2019 15:12:09 -0400 Message-ID: <15032.1561403529@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stephen Frost writes: > Stephen and Magnus want a warning, because it's an indication that a > tool author, or *something* modified the file in an unexpected way, and > that we are having to do some kind of cleanup on the file because of it. But you're presuming something that not everybody agrees with, which is that this situation should be considered unexpected. In particular, in order to consider it unexpected, you have to suppose that the content rules for postgresql.auto.conf are different from those for postgresql.conf (wherein we clearly allow last-one-wins). Can you point to any user-facing documentation that says that? regards, tom lane