pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
To: Christoph Berg <myon@debian.org>
To: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Collation versioning
Date: Thu, 6 Sep 2018 21:01:14 +0200
Message-ID: <b7ce31bb-dfe5-c689-06c4-3a8536f73e6a@2ndquadrant.com> (raw)
In-Reply-To: <CAEepm=3mKYhXS9NQCsPkGhkQxKAeZwbDneZV7QYKTDDYstTxZA@mail.gmail.com>
References: <CAEepm=0hoACQLFn8ro7jCO9-wTth2mXXS3K=s09gxKqN2jy8pA@mail.gmail.com>
<CAEepm=3a5BC7CwsXZo3V4fw6YuAMT2nJ1krwtqOatb=vDqRWEA@mail.gmail.com>
<20180905191014.GA29241@msg.df7cb.de>
<CAEepm=3mKYhXS9NQCsPkGhkQxKAeZwbDneZV7QYKTDDYstTxZA@mail.gmail.com>
On 05/09/2018 23:18, Thomas Munro wrote:
> On Wed, Sep 5, 2018 at 12:10 PM Christoph Berg <myon@debian.org> wrote:
>>> So, it's not ideal but perhaps worth considering on the grounds that
>>> it's better than nothing?
>>
>> Ack.
>
> Ok, here's a little patch like that.
>
> postgres=# select collname, collcollate, collversion from pg_collation
> where collname = 'en_NZ';
> collname | collcollate | collversion
> ----------+-------------+-------------
> en_NZ | en_NZ.utf8 | 2.24
> (1 row)
But wouldn't that also have the effect that glibc updates that don't
change anything about the locales would trigger the version
incompatibility warning?
Also, note that this mechanism only applies to collation objects, not to
database-global locales. So most users wouldn't be helped by this approach.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
view thread (188+ messages) latest in thread
Message-ID: <b7ce31bb-dfe5-c689-06c4-3a8536f73e6a@2ndquadrant.com>
Permalink: ../b7ce31bb-dfe5-c689-06c4-3a8536f73e6a@2ndquadrant.com/
Also on: postgresql.org/message-id/b7ce31bb-dfe5-c689-06c4-3a8536f73e6a@2ndquadrant.com
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, thomas.munro@enterprisedb.com, myon@debian.org
Subject: Re: Collation versioning
In-Reply-To: <b7ce31bb-dfe5-c689-06c4-3a8536f73e6a@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