Re: cache lookup failed error for partition key with custom opclass
Rushabh Lathia <rushabh.lathia@gmail.com>
From: Rushabh Lathia <rushabh.lathia@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2017-07-26T06:31:44Z
Lists: pgsql-hackers
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
Commits
-
Be more consistent about errors for opfamily member lookup failures.
- 278cb4341103 10.0 landed