| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andreas Seltenreich <seltenreich(at)gmx(dot)de>, Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Failed assertion in joinrels.c |
| Date: | 2016-08-08 12:30:22 |
| Message-ID: | CAFiTN-uRXwc51ywPKTLhK1Jtz6JzwmAPXKMK11pivj7o85_x5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 8, 2016 at 5:23 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2016-08-08 12:51:35 | Re: No longer possible to query catalogs for index capabilities? |
| Previous Message | Amit Kapila | 2016-08-08 11:53:12 | Re: [sqlsmith] Failed assertion in joinrels.c |