Re: OWNER TO on all objects

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OWNER TO on all objects
Date: 2004-06-15 17:01:57
Message-ID: 200406151901.57166.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne wrote:
> The old pg_dump would output a session auth, and then wouldn't bother
> changing it until necessary. However, with ALTER OWNER, I have to
> dump it for every object, even if it's the same user.

Well, the advantage of SET SESSION AUTHORIZATION is that it is SQL
compliant, whereas ALTER OWNER is not. So I'm in favor of changing
nothing. The examples you listed in you original mail, where the
privilege to do something was later dropped so the original state is
not reproducible, are to me examples that the privilege system is
flawed. You could use ALTER OWNER in those cases only, because those
states are not SQL compliant anyway.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2004-06-15 17:04:01 Re: OWNER TO on all objects
Previous Message Peter Eisentraut 2004-06-15 16:55:42 Re: #postgresql report