Horton
Menu

Re: plpgsql_check_function - rebase for 9.3

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Peter Eisentraut <peter_e@gmx.net>, Steve Singer <steve@ssinger.info>, Josh Berkus <josh@agliodbs.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-12-10T20:50:58Z
Lists: pgsql-hackers 
Robert Haas <robertmhaas@gmail.com> writes:
> This is a very good point.  Annotating the function itself with
> markers that cause it to be more strictly checked will create a
> dump/reload problem that we won't enjoy solving.  The decision to
> check the function more strictly or not would need to be based on some
> kind of session state that users could establish but dump restore
> would not.

One would hope that turning off check_function_bodies would be sufficient
to disable any added checking, though, so I don't see this being a problem
for pg_dump.  But there might be other scenarios where an additional knob
would be useful.

			regards, tom lane