Postgres Pro
Downloads
Home   >   mailing lists

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 4543.1500992027@sss.pgh.pa.us
Whole thread Raw
In response to Re: [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
Tree view 
Rushabh Lathia <rushabh.lathia@gmail.com> writes:
> On Mon, Jul 24, 2017 at 7:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> I go thorough the get_opfamily_proc() in the system and added the
> check for InvalidOid.

Think I did that already, please compare your results with
278cb4341103e967189997985b09981a73e23a34
        regards, tom lane

pgsql-hackers by date:

Previous
From: Alexey Bashtanov
Date:
Subject: [HACKERS] estimation for join results cardinality is sometimes more than theproduct of the downstream nodes'
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] [SQL] Postgresql “alter column type” creates an event which contains “temp_table_xxx”