Re: pg_collation_actual_version() ERROR: cache lookup failed for collation 123 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_collation_actual_version() ERROR: cache lookup failed for collation 123
Date
Msg-id YC4UIOaPTk1wxDms@paquier.xyz
Whole thread Raw
In response to Re: pg_collation_actual_version() ERROR: cache lookup failed for collation 123  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Thu, Feb 18, 2021 at 10:45:53AM +1300, Thomas Munro wrote:
> I guess I was trying to preserve a distinction between "unknown OID"
> and "this is a collation OID, but I don't have version information for
> it" (for example, "C.utf8").  But it hardly matters, and your
> suggestion works for me.  Thanks for looking!

Could you just add a test with pg_collation_current_version(0)?

+       pg_strncasecmp("POSIX.", collcollate, 6) != 0)
I didn't know that "POSIX." was possible.

While on it, I guess that you could add tab completion support for
CREATE COLLATION foo FROM.  And shouldn't CREATE COLLATION complete
with the list of existing collation?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Asynchronous Append on postgres_fdw nodes.
Next
From: Peter Eisentraut
Date:
Subject: Re: Is it worth accepting multiple CRLs?