Re: Simplify pg_collation.collversion for Windows libc - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Simplify pg_collation.collversion for Windows libc
Date
Msg-id 8bfe6c43-1cc0-1750-baec-fd168002d244@eisentraut.org
Whole thread Raw
In response to Re: Simplify pg_collation.collversion for Windows libc  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On 06.06.23 03:21, Thomas Munro wrote:
> On Mon, Jun 5, 2023 at 12:56 PM Daniel Verite <daniel@manitou-mail.org> wrote:
>> postgres=# select collversion,count(*) from pg_collation group by
>> collversion;
>>    collversion  | count
>> ---------------+-------
>>                 |     5
>>   1539.5,1539.5 |  1457
>> (2 rows)
>>
>> According to [1] the second number is obsolete, and AFAICS we should
>> expose only the first.
> 
> Would it be a good idea to remove or ignore the trailing /,*$/
> somewhere, perhaps during pg_upgrade, to avoid bogus version mismatch
> warnings?

I wonder whether it's worth dealing with this, versus just leaving it 
all alone.



pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Return value of pg_promote()
Next
From: Michael Paquier
Date:
Subject: Re: 回复:Fix missing initialization of delayChkptEnd