Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I believe the reason for
>> not changing it was that it seemed too likely to break existing
>> functions, with potentially nasty consequences if they chanced to be
>> security definers.
> Is this actually true or did we just forget it? :-)
I recall thinking about the point. The decision could've been wrong ...
regards, tom lane
--
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs