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