Postgres Pro
Downloads
Home   >   mailing lists

Re: [sqlsmith] Failed assertion in joinrels.c - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: [sqlsmith] Failed assertion in joinrels.c
Date
Msg-id CAFiTN-uOcV78Nk46YL4n+V4Hw8cGyZyDc6LnE335UKTS46VwdA@mail.gmail.com
Whole thread Raw
In response to Re: [sqlsmith] Failed assertion in joinrels.c  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [sqlsmith] Failed assertion in joinrels.c  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Aug 9, 2016 at 6:49 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> Okay, then how about ERRCODE_UNDEFINED_OBJECT?  It seems to be used in
> almost similar cases.

This seems better, after checking at other places I found that for
invalid type we are using ERRCODE_UNDEFINED_OBJECT and for invalid
functions we are using ERRCODE_UNDEFINED_FUNCTION. So I have done the
same way.

Updated patch attached.

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

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: dsm_unpin_segment
Next
From: Michael Paquier
Date:
Subject: Re: multivariate statistics (v19)