Re: pg_am.amowner - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_am.amowner
Date
Msg-id 12568.959826372@sss.pgh.pa.us
Whole thread Raw
In response to pg_am.amowner  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_am.amowner
Re: pg_am.amowner
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> It seems that access methods nominally have an "owner", but that owner is
> nowhere else referenced. Since there is no user interface for adding
> access methods anyway, would there be any problems with removing that
> field?

Hmm ... offhand I'm having a hard time seeing that it would make sense
to associate protection checks with an access method.  The only use
I can see for the owner field is to control who could delete an access
method --- and I don't have much problem with saying "only the
superuser".  It's even harder to believe that we'd really want non-
superusers installing access methods.

But the other side of the coin is what harm is it doing?  Surely you're
not worried about the space occupied by the column ;-)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: more cvs problems
Next
From: Bruce Momjian
Date:
Subject: Re: pg_am.amowner