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

From Brett McCormick
Subject Re: [HACKERS] Permissions on copy
Date
Msg-id 199802202211.OAA15363@abraxas.scene.com
Whole thread Raw
In response to Re: [HACKERS] Permissions on copy  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: [HACKERS] Permissions on copy  (jwieck@debis.com (Jan Wieck))
List pgsql-hackers
either-or or just a select, so it is forced to go through the
executor?  If we do that, what about reload the database..  it seems
like copy should just dump the table as-is and not do funny tricks
that make it impossible to COPY FROM...

On Fri, 20 February 1998, at 12:10:29, The Hermit Hacker wrote:

> > 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...
>
>

pgsql-hackers by date:

Previous
From: Humberto Rondon Parra
Date:
Subject: Unsubscribe
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Here it is - view permissions