Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbXKJ-0007Mn-Ki for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 20 May 2020 22:36:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jbXKI-0003V5-Ht for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 20 May 2020 22:36:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbXKI-0003Uy-Cz for pgsql-pkg-yum@lists.postgresql.org; Wed, 20 May 2020 22:36:38 +0000 Received: from wforward1-smtp.messagingengine.com ([64.147.123.30]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbXKF-0008LZ-HV for pgsql-pkg-yum@postgresql.org; Wed, 20 May 2020 22:36:37 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id 6B716CCB; Wed, 20 May 2020 18:36:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 20 May 2020 18:36:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=ozKYU2+5la+o80xQgSVZTsxC/xbFr9b/BQMIAilzp 90=; b=lBU1ZpRA87UaCGeO8SVLP/Pyjbs13YqIMuv/liaC3sulTODWS+Iwqg9Jj ljgQOSvOQPcWfvvLu/zuCOGuKUg4atYXbVVdX4YjmhKqS5dpQUrym7mSIlXDNo/S yZ+ESk1iUjtT8Onh5SyhaYH8lSd0DdQJ8ELG4ijgJChpr/O9VVOySOftwW809za9 1g4CDYpAh8xhuziu92CRpE889ss1JqFmUR2wjjaBogFu3BQbKO9GfHCF+gN1WSwW 32LQXVD/QIpZNTJTML0YOWYOvLhW4vwO4oZpBaE++JeTXBLiRaHFjDma/JLbH1Id FTZyjTHYGIYfNxM6QDXppunQgYTJA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddutddguddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeehnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuggftrfgrthhtvghrnhepveeuteelvdeuudfggfev udegudfhvdekgeeufefhtdeguedugefhheeugeefhfeinecuffhomhgrihhnpedvnhguqh hurggurhgrnhhtrdgtohhmnecukfhppeelfedrvdegfedrkedvrddvgeeinecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghish gvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p5df352f6.dip0.t-ipconnect.de [93.243.82.246]) by mail.messagingengine.com (Postfix) with ESMTPA id 3C212328005E; Wed, 20 May 2020 18:36:31 -0400 (EDT) Subject: Re: Can we stop defaulting to 'ident'? To: Stephen Frost References: <7761d006b5ace13a4d86ce489123e5004aaf8b6c.camel@gunduz.org> <20200519212710.GQ13712@tamriel.snowman.net> <6089d4c8e262dd6fe8a6510c283e674543a24b5c.camel@gunduz.org> <3869d8c9-c212-8d73-52f4-13b03abe4813@2ndquadrant.com> <20200520134035.GD296739@msg.df7cb.de> <3a7d55ed-6abb-2005-23d7-8411bb9f5651@2ndquadrant.com> <20200520145752.GD3418@tamriel.snowman.net> <32b7fe66-f0e6-42e5-3c95-7d123e7d7f6d@2ndquadrant.com> <20200520153337.GE3418@tamriel.snowman.net> Cc: Christoph Berg , =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , Craig Ringer , pgsql-pkg-yum From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <074a1634-450f-1e2f-53aa-178de3ac1076@2ndquadrant.com> Date: Thu, 21 May 2020 00:36:30 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20200520153337.GE3418@tamriel.snowman.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-05-20 17:33, Stephen Frost wrote: >> But this leads to other questions, like, what should pg_upgrade do? > Same as it always has- make the user deal with anything they need to > regarding postgresql.conf? Why would anything change with pg_upgrade? Well, one might expect that the user at least gets some kind of notification that something is changing. What happens when you end up with a mix of MD5 and SCRAM passwords in pg_authid? Are users going to be notified about this somehow? Has this been thought through to the end? Have all combinations been tested? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services