| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: restructuring "alter table" privilege checks |
| Date: | 2010-01-24 03:16:26 |
| Message-ID: | 603c8f071001231916u518d60daw1c272e2c327ae795@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jan 23, 2010 at 10:11 PM, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> If we put the new ATSimplePermissions() with all the needed information
> just after gathering them at the execution stage, we don't need to have
> some of exceptions which takes additional checks except for ownership
> on the relation to be altered.
Maybe I'm still not understanding, but I don't see how you're going to
do this without a massive pile of spaghetti code and a function with
about 12 parameters. Feel free to show some code, but I think this is
a non-starter.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-24 03:29:23 | Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns |
| Previous Message | KaiGai Kohei | 2010-01-24 03:11:34 | Re: restructuring "alter table" privilege checks |