Re: [GENERAL] What user to defaults execute as?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] What user to defaults execute as?
Date: 2002-11-02 06:01:11
Message-ID: 18244.1036216871@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas T. Thai 2002-11-02 06:58:34 unique in two not so unique columns
Previous Message Bruno Wolff III 2002-11-02 05:55:42 Re: [GENERAL] What user to defaults execute as?

Browse pgsql-hackers by date

  From Date Subject
Next Message Steve Howe 2002-11-02 08:29:12 "Cache lookup failed for relation 16905" ??
Previous Message Bruno Wolff III 2002-11-02 05:55:42 Re: [GENERAL] What user to defaults execute as?