Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] column-level update privs + lock table

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 (view raw or whole thread)
Lists: pgsql-generalpgsql-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 


This is the crux of the debate. Why should this inconsistency be allowed
to continue?

Are there covert channel issues here, KaiGai?

 Simon Riggs 
 PostgreSQL Development, 24x7 Support, Training and Services

In response to


pgsql-hackers by date

Next:From: Rob WultschDate: 2010-11-30 13:18:12
Subject: Re: crash-safe visibility map, take three
Previous:From: Itagaki TakahiroDate: 2010-11-30 11:13:37
Subject: Re: Tab completion for view triggers in psql

pgsql-general by date

Next:From: hubert depesz lubaczewskiDate: 2010-11-30 13:21:09
Subject: Re: PostgreSQL hanging on new connections?
Previous:From: Alexander FarberDate: 2010-11-30 10:47:08
Subject: Re: select max()

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group