Re: [HACKERS] cache lookup failed error for partition key with custom opclass

Поиск
Список
Период
Сортировка
От Rushabh Lathia
Тема Re: [HACKERS] cache lookup failed error for partition key with custom opclass
Дата
Msg-id CAGPqQf0=p9D4oPS2uhqztn00ZBgpCdLrN_AXwO0AwnN6-n7RbQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] cache lookup failed error for partition key with custom opclass  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] cache lookup failed error for partition key with custom opclass  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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
www.EnterpriseDB.com
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rafia Sabih
Дата:
Сообщение: Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables
Следующее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: [HACKERS] PgFDW connection invalidation by ALTER SERVER/ALTERUSER MAPPING