Re: [HACKERS] cache lookup failed error for partition key with custom opclass - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] cache lookup failed error for partition key with custom opclass
Date
Msg-id 30188.1500904386@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] cache lookup failed error for partition key with custom opclass  (Rushabh Lathia <rushabh.lathia@gmail.com>)
Responses Re: [HACKERS] cache lookup failed error for partition key with custom opclass
List pgsql-hackers
Rushabh Lathia <rushabh.lathia@gmail.com> writes:
> PFA patch, where added elog() to add the error message same as all other
> places.

Some looking around says that this *isn't* the only place that just
blithely assumes that it will find an opfamily entry.  But I agree
that not checking for that isn't up to project standards.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: [HACKERS] cache lookup failed error for partition key with custom opclass
Next
From: Gilles Darold
Date:
Subject: [HACKERS] Issue with circular references in VIEW