Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ... - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...
Date
Msg-id 3115.1065239742@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-committers
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> Add GUC parameter check_function_bodies to control whether validation
>> of function bodies is done at CREATE FUNCTION time.

> If it's only honored by SQL functions, then it should probably be called
> check_sql_function_bodies.

I thought about that while I was making the patch, but decided that it
would be a very un-forward-looking name.  Someday we will probably have
syntax-checking validators for plpgsql, etc.

The original version of the patch actually suppressed calling the
validator altogether, but I soon realized that wouldn't do --- it
would allow you to create SQL functions with unsupported pseudotype
arguments or results, for example.  Further thought led me to decide
explicitly not to suspend checking of internal and C function
references, on the grounds that if they are broken they'd still be
broken at the completion of the restore script, and so we'd only
be losing the ability to report the problem.

So the fact that it only affects SQL functions at the moment is IMHO
just happenstance; the scope of what it does will change as we add more
validation capability.

            regards, tom lane

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql-server/ /INSTALL oc/src/sgml/installatio ...
Next
From: petere@svr1.postgresql.org (Peter Eisentraut - PostgreSQL)
Date:
Subject: pgsql-server/src/backend/po hr.po