Postgres Pro
Downloads
Home   >   mailing lists

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

From Rushabh Lathia
Subject Re: [HACKERS] cache lookup failed error for partition key with custom opclass
Date
Msg-id CAGPqQf0yAWoB+td8tuiGzEufsskgAE2TcRy6bFx0O34fhqgsWQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] cache lookup failed error for partition key with custom opclass  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view


On Tue, Jul 25, 2017 at 7:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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

Thanks Tom.
 

                        regards, tom lane



--
Rushabh Lathia

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] [BUGS] BUG #14759: insert into foreign data partitions fail
Next
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables