| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] column-level update privs + lock table |
| Date: | 2010-11-30 12:26:57 |
| Message-ID: | 1291120017.4634.9899.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, 2010-11-29 at 21:37 -0500, Josh Kupershmidt wrote:
> I still see little reason to make LOCK TABLE permissions different for
> column-level vs. table-level UPDATE privileges
Agreed.
This is the crux of the debate. Why should this inconsistency be allowed
to continue?
Are there covert channel issues here, KaiGai?
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2010-11-30 13:21:09 | Re: PostgreSQL hanging on new connections? |
| Previous Message | Alexander Farber | 2010-11-30 10:47:08 | Re: select max() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Wultsch | 2010-11-30 13:18:12 | Re: crash-safe visibility map, take three |
| Previous Message | Itagaki Takahiro | 2010-11-30 11:13:37 | Re: Tab completion for view triggers in psql |