| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms(). |
| Date: | 2010-07-09 18:17:36 |
| Message-ID: | 1278699456.29736.1039.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Fri, 2010-07-09 at 14:01 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > On Fri, 2010-07-09 at 13:21 -0400, Tom Lane wrote:
> >> Except that it *is* a change in behavior: the first check will occur
> >> too soon.
>
> > Sooner matters why?
>
> Consider PREPARE followed only later by EXECUTE. Your proposal would
> make the PREPARE fail outright, when it currently does not.
Just to avoid wasted investigation: are you saying that is important
behaviour that is essential we retain in PostgreSQL, or will you hear
evidence that supporting that leads to a performance decrease elsewhere?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-07-09 21:11:48 | pgsql: Fix ruleutils' get_variable() to print something useful for Vars |
| Previous Message | Tom Lane | 2010-07-09 18:01:11 | Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms(). |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-07-09 18:49:50 | Re: WIP patch for serializable transactions with predicate locking |
| Previous Message | Joshua D. Drake | 2010-07-09 18:03:54 | Re: FYI: Ubuntu 10.04 lucid strange segfault |