Re: [sqlsmith] Failed assertion in joinrels.c

Поиск
Список
Период
Сортировка
От Dilip Kumar
Тема Re: [sqlsmith] Failed assertion in joinrels.c
Дата
Msg-id CAFiTN-uRXwc51ywPKTLhK1Jtz6JzwmAPXKMK11pivj7o85_x5A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [sqlsmith] Failed assertion in joinrels.c  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: [sqlsmith] Failed assertion in joinrels.c  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers

On Mon, Aug 8, 2016 at 5:23 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> Your other options and the option you choose are same.
>

Sorry typo, I meant ERRCODE_INVALID_OBJECT_DEFINITION. 

 
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.

However I can change error message to "type id %u does not exit" if this seems better ?

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: [sqlsmith] Failed assertion in joinrels.c
Следующее
От: Dave Cramer
Дата:
Сообщение: Re: No longer possible to query catalogs for index capabilities?