Re: [HACKERS] Permissions on copy

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Andreas(dot)Zeugswetter(at)telecom(dot)at (Zeugswetter Andreas SARZ)
Cc: pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] Permissions on copy
Date: 1998-02-20 15:45:30
Message-ID: 199802201545.KAA04593@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Since the copy statement is behaving differently than the normal select
> stuff,
> I think we should eighter introduce a new permission (name it copy or dump)
> or include the copy into the rewrite system.
>
> I would vote for the first and implement a new command:
> unload to <filename> [delimiter '|'] <select statement>; -- and
> load from <filename> [delimiter '|'] <insert statement>;
> that does behave like the select. (please forgive my Informix
> background)

Yes, I agree the Informix way of having load/unload, and having a SELECT
capability so you can dump any data/join you want, not just a single
table. Do I have votes to put this on the TODO list?

>
> As to the topic with setuid triggers and others, I think setuid procedures
> would be sufficient.
> These are implemented in Informix with the following simple syntax:
> create dba procedure ....
>
> Andreas
>
>

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-02-20 16:04:16 Re: [HACKERS] How To free resources used by large object Relations?
Previous Message Thomas G. Lockhart 1998-02-20 15:42:05 Re: [HACKERS] Subselects and NOTs