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 1kIA38-0004ZJ-26 for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Sep 2020 12:27:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kIA35-0008MI-28 for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Sep 2020 12:27:03 +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 1kIA34-0008M8-QU for pgsql-hackers@lists.postgresql.org; Tue, 15 Sep 2020 12:27:02 +0000 Received: from forward1-smtp.messagingengine.com ([66.111.4.223]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIA2x-0001A9-Ko for pgsql-hackers@postgresql.org; Tue, 15 Sep 2020 12:27:01 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id CA27019422F2; Tue, 15 Sep 2020 08:26:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 15 Sep 2020 08:26:52 -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=fm3; bh=VU4W5eyKTLOnU1wrZcBtDffZ0HmV72DTcIp2dFkHt AQ=; b=lcUK1v2xiOTQoMGVrhAzMnywuGYQTPSnm3S7Y/WWX5STtZmCFrrJOKS/l zhz+pZC3qq8NL+/DPmgLmjWUJnAnydioMcrJfP+CxRD099xRxtS+23CI7p2goubg 0BOgrJCIurf+O+cVNFMpk0LigBQ8euwld7tNmuIPhHKoLHJXnDrZDE/JoJ8HC1ug lRCmilM9nFV6Bgjw6Q6y8NrgK14eqDPVAHGIGrk5db655PZy8lEDjB7X6OlJrCZt cT+Tfdu/FAQQvwEwSkgLtJAljh1A1219QTEuw9WVnLMnvJhr7827fVkh0n76RapF g7kt2n4rfThQKJGEy30ov3Y9UREhg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrtddtgddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhfhokffffgggjggtgfesthejredttdefheenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqh hurggurhgrnhhtrdgtohhmqeenucggtffrrghtthgvrhhnpeekgfdttdejiefgieegtddv udeigeffteekgfdtfeekgefhgeegueelfeeffeefgeenucffohhmrghinhepphgrthgthh drihhmpddvnhguqhhurggurhgrnhhtrdgtohhmnecukfhppeelfedrvddtvddrvdehuddr feegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepph gvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p5dcafb22.dip0.t-ipconnect.de [93.202.251.34]) by mail.messagingengine.com (Postfix) with ESMTPA id 022B0328005A; Tue, 15 Sep 2020 08:26:50 -0400 (EDT) Subject: Re: Collation versioning To: Julien Rouhaud , Michael Paquier References: <20200708062620.GD18003@paquier.xyz> <13b0c950-80f9-4c10-7e0f-f59feac56a98@2ndquadrant.com> <20200813095204.f7mlgdzsbaxa3mzr@nol> <20200814073746.GF2057@paquier.xyz> <20200814090235.ifld2qvaw43pzpzg@nol> <20200907031741.GK2455@paquier.xyz> <20200908144507.GA57691@nol> Cc: Thomas Munro , Robert Haas , Laurenz Albe , Douglas Doole , Christoph Berg , Pg Hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Tue, 15 Sep 2020 14:27:38 +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: <20200908144507.GA57691@nol> 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-09-08 16:45, Julien Rouhaud wrote: > I usually agree with that approach, I'm just afraid that getting a consensus on > the best way to do that will induce a lot of discussions, while this is > probably a corner case due to general usage of hash and bloom indexes. > > Anyway, in order to make progress on that topic I attach an additional POC > commit to add the required infrastructure to handle this case in > v29-0001-Add-a-new-amnostablecollorder-flag-in-IndexAmRou.patch. I'm confused now. I think we had mostly agreed on the v28 patch set, without this additional AM flag. There was still some discussion on what the AM flag's precise semantics should be. Do we want to work that out first? Btw., I'm uneasy about the term "stable collation order". "Stable" has an established meaning for sorting. It's really about whether the AM uses collations at all, right? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services