From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: temporary functions (and other object types) |
Date: | 2010-11-06 19:18:11 |
Message-ID: | 23241.1289071091@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I guess. If you search pg_temp always then it's pretty much
> impossible to avoid having a security hole, if you use any non-trivial
> SQL. But if you search pg_temp for non-SD only then you'll only have
> a security hole if you assume (presumably without testing) that the
> behavior is the same in that case. If an SD function is calling
> temporary functions they'd best be ones it created, otherwise your
> security is pretty much nonexistent anyway.
In general I don't see a lot of use for calling temp functions that
you don't know are temp functions. So I see nothing much wrong with
having to use the pg_temp. prefix --- and the possibility of security
issues definitely pushes me over the line to being happy with requiring
that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-11-06 20:25:41 | Re: IA64 versus effective stack limit |
Previous Message | Robert Haas | 2010-11-06 19:02:56 | Re: temporary functions (and other object types) |