| From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Question about STRICT |
| Date: | 2009-06-03 16:40:55 |
| Message-ID: | 4A26A797.70206@xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Gevik Babakhani <pgdev(at)xs4all(dot)nl> writes:
>> Perhaps it is an idea to have something like:
>> "RAISE ERROR ON NULL INPUT"
>
> [ shrug... ] There's really been no demand for that. If you want a
> particular function to do it, you can put suitable tests and error
> reports into that function. I can't see us adding extra cycles into
> the core function-calling code (which is a very hot hot-spot) for a
> feature with so little demand.
Understood. Thank you (Tom and Greg) for clarifying this.
--
Regards,
Gevik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-03 16:42:40 | Re: Plan time Improvement - 64bit bitmapset |
| Previous Message | Andrew Dunstan | 2009-06-03 16:38:33 | Re: Managing multiple branches in git |