From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] remove redundant ownership checks |
Date: | 2009-12-18 02:28:10 |
Message-ID: | 603c8f070912171828g66a935bcvd34a2cf6c0f9707f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 17, 2009 at 7:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If we're going to start moving these checks around we need a very
> well-defined notion of where permissions checks should be made, so that
> everyone knows what to expect. I have not seen any plan for that.
> Removing one check at a time because it appears to not be necessary
> in the code paths you've looked at is not a plan.
I'm not completely familiar with the existing code structure here, but
it sort of seems like in general you might want to divide up the
processing of a statement into a parse analysis phase, a permissions
checking phase, and an execution phase. The parse analysis seems to
be mostly separated out into transformXyz() functions, but the
permissions checking is mixed in with the execution. Disentangling
that seems like a job and a half.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-12-18 02:42:19 | Re: Streaming replication and non-blocking I/O |
Previous Message | Robert Haas | 2009-12-18 02:15:50 | Re: patch - per-tablespace random_page_cost/seq_page_cost |