Re: Question about STRICT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Cc: Greg Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Question about STRICT
Date: 2009-06-03 15:40:02
Message-ID: 5472.1244043602@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2009-06-03 15:48:02 Plan time Improvement - 64bit bitmapset
Previous Message flippo00110001 2009-06-03 15:38:39 Postgres delays function returning large set of data