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-24T13:53:06Z
Lists: pgsql-hackers
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. regards, tom lane
Commits
-
Be more consistent about errors for opfamily member lookup failures.
- 278cb4341103 10.0 landed