On Tue, 27 May 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> I applied a docs patch for this, though not exactly what you sent in.
A lot better. Thanks for your interest. Let's see if I'll ask same
question next year.
Regards.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
[EMAIL PROTECTED] (Volkan =?utf-8?B?WWF6xLFjxLE=?=) writes:
> On Tue, 27 May 2008, Tom Lane <[EMAIL PROTECTED]> writes:
>> Well, you tested wrong then. It works as expected for me, which is
>> that you need SELECT if the query involves fetching any existing
>> column value:
> Pff... Sorry for the
On Tue, 27 May 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> Well, you tested wrong then. It works as expected for me, which is
> that you need SELECT if the query involves fetching any existing
> column value:
Pff... Sorry for the noise. (I created example table under a differrent
schema than "pu
[EMAIL PROTECTED] (Volkan =?utf-8?B?WWF6xLFjxLE=?=) writes:
> On Tue, 27 May 2008, Tom Lane <[EMAIL PROTECTED]> writes:
>> You don't have SELECT privilege, which is required to read any of the
>> columns in the WHERE clause.
> As far as I tested, even
> DELETE FROM foo;
> UPDATE foo SET bar =
Hi,
I rarely use GRANT -- nearly once every 1-2 year -- and everytime I
forget this small detail: DELETE/INSERT/UPDATE privileges require SELECT
privilege also.
On Tue, 27 May 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> You don't have SELECT privilege, which is required to read any of the
> colu
