On Fri, Mar 09, 2007 at 01:07:23 -0500,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Certainly --- the point here is merely that that isn't the *default*
> behavior. We judged quite some time ago that allowing public execute
> access was the most useful default. Perhaps that was a bad choice, but
> I think we're unlikely to change it now ...
At the time this choice was being made it was realized there was going to
be a lot of pain for people updating, as the previous releases didn't
limit access to functions. So it was unlikely to change then, for the same
reasons it is unlikely to change now.
