Re: Simplify pg_collation.collversion for Windows libc

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Simplify pg_collation.collversion for Windows libc
Date: 2023-06-06 11:09:00
Message-ID: 8bfe6c43-1cc0-1750-baec-fd168002d244@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.06.23 03:21, Thomas Munro wrote:
> On Mon, Jun 5, 2023 at 12:56 PM Daniel Verite <daniel(at)manitou-mail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-06-06 11:19:12 Re: 回复:Fix missing initialization of delayChkptEnd
Previous Message Ashutosh Sharma 2023-06-06 11:05:58 Return value of pg_promote()