Bruce Momjian <[EMAIL PROTECTED]> writes:
> The problem is that the more complex you make things, the easier it is
> to make a mistake. That's why I like our simpler model unless there is
> a glaring problem with it.
I think Bruno's got a good point. The implementation would be kind of
painful, so I've been trying to think of a reason to object to it, but
so far I don't see one ;-(
The example of a serial column (DEFAULT nextval('foo_seq')) seems
compelling. You do not really want to grant general-purpose UPDATE
rights on foo_seq to everyone you might allow to INSERT into your
table.
And I have not yet been able to think of a concrete case where the
existing behavior (execute as calling user) is better.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
