Re: cache lookup failed for collation 0 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: cache lookup failed for collation 0
Date
Msg-id eb348ff1-4bc6-412d-9619-ec72a95d9372@2ndquadrant.com
Whole thread Raw
In response to Re: cache lookup failed for collation 0  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
List pgsql-hackers
On 2019-04-15 07:44, Jeevan Chalke wrote:
>     The root cause is that the same code match_pattern_prefix() is being
>     used for text and bytea, but bytea does not use collations, so having
>     the collation 0 is expected, and we shouldn't call
>     get_collation_isdeterministic() in that case.
> 
>     Proposed patch attached.
> 
> Looks fine to me.

Committed, thanks.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Floris Van Nee
Date:
Subject: Re: partitioning performance tests after recent patches
Next
From: zedaardv@gmail.com
Date:
Subject: Re: PANIC: could not flush dirty data: Operation not permitted power8, Redhat Centos