Re: Collation versioning

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Christoph Berg <myon(at)debian(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Collation versioning
Date: 2019-10-09 19:37:59
Message-ID: 2df246f1-a1f5-8344-9100-be53736f68c0@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Timmy Siu 2019-10-09 19:54:55 TCP Wrappers
Previous Message Dent John 2019-10-09 19:26:14 Re: [PATCH] Do not use StdRdOptions in Access Methods