Re: cache lookup failed for collation 0
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeevan Chalke <jeevan.chalke@enterprisedb.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-04-11T17:20:41Z
Lists: pgsql-hackers
Jeevan Chalke <jeevan.chalke@enterprisedb.com> writes: > Do you mean, the code in get_collation_isdeterministic() should look like > something like below? > If colloid = InvalidOid then > return TRUE > ELSE IF tuple is valid then > return collisdeterministic from the tuple > ELSE > return FALSE I think it's appropriate to fail if we don't find a tuple, for any collation oid other than zero. Again, if you trace through the behavior of the longstanding collation check functions like lc_ctype_is_c(), you'll see that that's what happens (except for some hardwired OIDs that they have fast paths for). regards, tom lane
Commits
-
Unbreak index optimization for LIKE on bytea
- abb9c63b2c00 12.0 landed
-
Collations with nondeterministic comparison
- 5e1963fb764e 12.0 cited