AW: [HACKERS] Permissions on copy - Mailing list pgsql-hackers

From Zeugswetter Andreas SARZ
Subject AW: [HACKERS] Permissions on copy
Date
Msg-id 219F68D65015D011A8E000006F8590C6010A51EB@sdexcsrv1.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> > On Fri, 20 Feb 1998, Bruce Momjian wrote:
> >
> > > Two things.  First was a separate COPY priviledge, which I vote
> against.
> > > I see no real value to it, except to work around the problem that COPY
> > > doesn't use rules.
> >
> >     Okay, I may be totally out in left field here (ie. unrelated), but
> > what stops a user from doing a 'COPY out' on a table that they don't
> have
> > SELECT privileges on?  Kind of negates 'REVOKE ALL...', no?
>
> Yes I think a separate COPY permission makes no sense.
>
> > > Second, there was the idea of making copy allow a real select
> statement
> > > and not just a table name.  If we do that, all goes through the
> > > executor, and you get view and rules working properly.  May have some
> > > performance penalty, though it probabably will be minor.
> >
> >     This sounds reasonable...
> >
>
>
Just to make you comfortable, yes I also completely agree

Andreas



pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SARZ
Date:
Subject: AW: [HACKERS] triggers, views and rules (not instead)
Next
From: ocie@paracel.com
Date:
Subject: Re: [HACKERS] Subselects and NOTs