Re: [sqlsmith] Failed assertion in joinrels.c
От | Amit Kapila |
---|---|
Тема | Re: [sqlsmith] Failed assertion in joinrels.c |
Дата | |
Msg-id | CAA4eK1Js5kr4EZFCwYWtXpvvR1-65xTUuLueV-yH04Faq-oAgQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [sqlsmith] Failed assertion in joinrels.c (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: [sqlsmith] Failed assertion in joinrels.c
|
Список | pgsql-hackers |
On Mon, Aug 8, 2016 at 6:00 PM, Dilip Kumar <dilipbalaut@gmail.com> wrote: > On Mon, Aug 8, 2016 at 5:23 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> >> >> Did you consider to use ERRCODE_UNDEFINED_COLUMN with error messages >> like: "type %u does not exit" or "type id %u does not exit"? Errorcode >> ERRCODE_UNDEFINED_COLUMN seems to be used for syscache lookup failure >> cases at certain places in code. > > > But I think, OBJECT will be more appropriate than COLUMN at this place. > Okay, then how about ERRCODE_UNDEFINED_OBJECT? It seems to be used in almost similar cases. > However I can change error message to "type id %u does not exit" if this > seems better ? > I think that is better. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: