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 1mMDGM-0004Mq-CV for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Sep 2021 17:46:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mMDGL-0002k7-Cr for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Sep 2021 17:46:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mMDGL-0002ix-56 for pgsql-hackers@lists.postgresql.org; Fri, 03 Sep 2021 17:46:01 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mMDGH-0003Hs-C2 for pgsql-hackers@lists.postgresql.org; Fri, 03 Sep 2021 17:46:00 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id B0A4A32009DC; Fri, 3 Sep 2021 13:45:54 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 03 Sep 2021 13:45:54 -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:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=2GWzNEpy4xMjUh04BgexIFmEZBQ9tMqFzJPAtcv6DRk=; b=EMoBm6p6 X+iCy1YCF6XJxUIpQLRxoUKShrFTsNSMLLQfomKpujJKzsiE9QagZFR1sRaBX7qM 4gsDCk5RzhSYccKPjYzLPBHO9eieVUVbfy1PYUn+MSE7l5XqFbKksEXcg3jQSzX4 5pj3zxS1z9urvDVdbLyUPd6V1QbL678f1oRk5FouxCg80RKqDBKwwOqifutLrklD +yRDXT+3gB9UCQP8SnYxNql140yqDyn90UBkoJgfDYnRI/tgX+mGjWcnTbt+7PI9 YCn5GzqC5n6Z40FKESq/pMLxJ/muUHuyLEaWJCG8wRkFGtigpmT+OirYC98i6xRG WKdXnlfAT5JAHg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddvjedguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepudejveejffejveduudetvdekieeuiedtvdeileefkeev jedufeeguedvjefhueelnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 Sep 2021 13:45:53 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 02DE82A0744; Fri, 3 Sep 2021 13:45:51 -0400 (-04) Date: Fri, 3 Sep 2021 13:45:50 -0400 From: Alvaro Herrera To: John Naylor Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Set the volatility of the timestamptz version of date_bin() back Message-ID: <202109031745.2ukvwzuigtwk@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Sep-03, John Naylor wrote: > Set the volatility of the timestamptz version of date_bin() back to immutable > > 543f36b43d was too hasty in thinking that the volatility of date_bin() > had to match date_trunc(), since only the latter references > session_timezone. > > Bump catversion These catversion bumps in branch 14 this late in the cycle seem suspect. Didn't we have some hesitation to push multirange unnest around beta2 precisely because of a desire to avoid catversion bumps? -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/