Horton

Re: Collation versioning

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Christoph Berg <myon@debian.org>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-10-09T19:37:59Z
Lists: pgsql-hackers 
On 2019-10-09 21:19, Peter Eisentraut wrote:
> On 2019-10-03 14:25, Thomas Munro wrote:
>>> The only open question on this patch was whether it's a good version to
>>> use.  I think based on subsequent discussions, there was the realization
>>> that this is the best we can do and better than nothing.
>>>
>>> In the patch, I would skip the configure test and just do
>>>
>>> #ifdef __GLIBC__
>>>
>>> directly.
>>
>> Ok.  Here's one like that.
> 
> Pushed that.

Actually, I had to revert that because pg_dump and pg_upgrade tests need
to be updated, but that seems doable.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Doc: Document known problem with Windows collation versions.

  2. Add collation versions for FreeBSD.

  3. Tolerate version lookup failure for old style Windows locale names.

  4. Track collation versions for indexes.

  5. Add pg_depend.refobjversion.

  6. Remove pg_collation.collversion.

  7. Fix the MSVC build for versions 2015 and later.

  8. Add collation versions for Windows.

  9. Implement type regcollation

  10. Use libc version as a collation version on glibc systems.

  11. Make type "name" collation-aware.