pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Julien Rouhaud <rjuju123@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Douglas Doole <dougdoole@gmail.com>
Cc: Christoph Berg <myon@debian.org>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Collation versioning
Date: Tue, 15 Sep 2020 14:27:38 +0200
Message-ID: <c3324b4e-095d-8de9-c3ba-7b468bb5b0b4@2ndquadrant.com> (raw )
In-Reply-To: <20200908144507.GA57691@nol >
References: <CA+hUKGLrSHedEs=xgHxto6twnacbSZtC_rdZL+=Uv8jkPm1boA@mail.gmail.com >
<20200708062620.GD18003@paquier.xyz >
<13b0c950-80f9-4c10-7e0f-f59feac56a98@2ndquadrant.com >
<CAOBaU_Z1GgiiK__F2DbBzDM+xBb9Nxbe=4zszoOihRaZLyjNtA@mail.gmail.com >
<CA+hUKGKyL0B9Yz4cBBh7Yi-2UQ6XLLGifB0zxrPc1qxuh-KTEQ@mail.gmail.com >
<20200813095204.f7mlgdzsbaxa3mzr@nol >
<CA+hUKGLP-aW+K_PUCPbTy=g18yC=7UjurXXwiqYwTbtj3SwukA@mail.gmail.com >
<20200814073746.GF2057@paquier.xyz >
<20200814090235.ifld2qvaw43pzpzg@nol >
<20200907031741.GK2455@paquier.xyz >
<20200908144507.GA57691@nol >
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
view thread (188+ messages) latest in thread
Message-ID: <c3324b4e-095d-8de9-c3ba-7b468bb5b0b4@2ndquadrant.com>
Permalink: ../c3324b4e-095d-8de9-c3ba-7b468bb5b0b4@2ndquadrant.com/
Also on: postgresql.org/message-id/c3324b4e-095d-8de9-c3ba-7b468bb5b0b4@2ndquadrant.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, rjuju123@gmail.com, michael@paquier.xyz, thomas.munro@gmail.com, robertmhaas@gmail.com, laurenz.albe@cybertec.at, dougdoole@gmail.com, myon@debian.org
Subject: Re: Collation versioning
In-Reply-To: <c3324b4e-095d-8de9-c3ba-7b468bb5b0b4@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox