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 CAGPqQf0=p9D4oPS2uhqztn00ZBgpCdLrN_AXwO0AwnN6-n7RbQ@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>)
Responses Re: [HACKERS] cache lookup failed error for partition key with custom opclass
List pgsql-hackers


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

Thanks Tom.

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

Thanks,
Rushabh Lathia
Attachment

pgsql-hackers by date:

Previous
From: Rafia Sabih
Date:
Subject: Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] PgFDW connection invalidation by ALTER SERVER/ALTERUSER MAPPING