yazicivo@ttmail.com (Volkan =?utf-8?B?WWF6xLFjxLE=?=) writes:
> On Tue, 27 May 2008, Tom Lane <tgl@sss.pgh.pa.us> 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 "public" to be able to test effects of schema priviliges to
> INSERT/UPDATE/DELETE commands, but I somehow forgot that detail later.)
> I updated the doc patch.
I applied a docs patch for this, though not exactly what you sent in.
Thanks for pointing out the omission.
regards, tom lane
