| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Fix permission tests for views/tables proven empty by constraint |
| Date: | 2013-05-08 12:59:54 |
| Message-ID: | 20774.1368017994@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2013-05-07 21:45:02 -0400, Tom Lane wrote:
>> Well, it might fail to report a permissions violation when the
>> not-allowed-to-be-accessed relation could be proven to yield no rows.
> Couldn't it also cause tables not to be locked that ought to be? That
> seems to be the nastier part to me.
In ordinary immediate execution the parser or planner would have
obtained the relevant table lock. I think what you say is possible if a
prepared plan is re-executed, but TBH it doesn't sound like much of an
issue to me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-05-08 16:30:31 | Re: Re: [COMMITTERS] pgsql: Fix permission tests for views/tables proven empty by constraint |
| Previous Message | Heikki Linnakangas | 2013-05-08 11:36:55 | pgsql: Use the term "radix tree" instead of "suffix tree" for SP-GiST t |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karol Trzcionka | 2013-05-08 15:50:06 | RETURNING syntax for COPY |
| Previous Message | Alexander Korotkov | 2013-05-08 12:49:50 | Re: Terminology issue: suffix tree |