Re: [GENERAL] column-level update privs + lock table
От | Robert Haas |
---|---|
Тема | Re: [GENERAL] column-level update privs + lock table |
Дата | |
Msg-id | AANLkTi=4nKJWzJai_+EseevGHgEkVVzZ-SOfX4MVd1M0@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] column-level update privs + lock table (Josh Kupershmidt <schmiddy@gmail.com>) |
Ответы |
Re: [GENERAL] column-level update privs + lock table
|
Список | pgsql-hackers |
On Fri, Oct 15, 2010 at 3:49 PM, Josh Kupershmidt <schmiddy@gmail.com> wrote: > [Moving to -hackers] > > On Fri, Oct 15, 2010 at 3:43 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> On Mon, 2010-10-11 at 09:41 -0400, Josh Kupershmidt wrote: >>> On Thu, Oct 7, 2010 at 7:43 PM, Josh Kupershmidt <schmiddy@gmail.com> wrote: >>> >>> > I noticed that granting a user column-level update privileges doesn't >>> > allow that user to issue LOCK TABLE with any mode other than Access >>> > Share. >>> >>> Anyone think this could be added as a TODO? >> >> Seems so to me, but you raise on Hackers. > > Thanks, Simon. Attached is a simple patch to let column-level UPDATE > privileges allow a user to LOCK TABLE in a mode higher than Access > Share. Small doc. update and regression test update are included as > well. Feedback is welcome. Please add this to https://commitfest.postgresql.org/action/commitfest_view/open I want to look at this at some point, but we still have over a dozen patches from the current CF to deal with. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: