| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pl/pgsql enabled by default |
| Date: | 2005-05-09 04:00:21 |
| Message-ID: | 16567.1115611221@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Hm. If you incorrectly mark your function as IMMUTABLE even though it
> has side effects then the planner may indeed collapse this. Does the
> planner know it can't collapse views if the underlying tables aren't
> accessible to the user?
There are no cases where function or view collapsing elides permissions
checks (if you have a counterexample please provide it!!). They could
change the time at which permissions checks are applied, though; which
has the potential for a REVOKE to not disallow execution of already-
planned queries that ideally it should prevent. I believe that this
risk will be fixed by the planned forcing of replanning after schema
changes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Satoshi Nagayasu | 2005-05-09 04:03:10 | Re: Oracle Style packages on postgres |
| Previous Message | Tom Lane | 2005-05-09 03:54:06 | Re: [PATCHES] Cleaning up unreferenced table files |