Tom Lane <t...@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <kevin.gritt...@wicourts.gov> writes:
 
>> throw an error on any attempt to call a volatile function or
>> modify the database?
 
> It's *not an error* for a nonvolatile function to call a volatile
> one.
 
Right, we all know it currently doesn't throw an error, but I can't
think of anywhere I'd like to have someone do that in a database for
which I have any responsibility.  Does anyone have a sane use case
for a non-volatile function to call a volatile one or to update the
database?
 
-Kevin

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to