| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, dinesh kumar <dineshkumar02(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposing COPY .. WITH PERMISSIVE |
| Date: | 2015-11-16 02:05:02 |
| Message-ID: | 564939CE.80501@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/2/15 4:19 PM, Stefan Kaltenbrunner wrote:
> maybe - but having a fixed "default" is very different from baking a
> classic unix permission concept of user/group/world^others into actual
> DDL or into a COPY option. The proposed syntax might make some sense to
> a admin used to a unix style system but it is likely utterly
> incomprehensible to somebody who is used to (windows style) ACLs.
>
> I dont have a good answer on what to do else atm but I dont think we
> should embedded traditional/historical unix permission models in our
> grammer unless really really needed...
The user can just create a directory with appropriate permissions and
copy the files there. I don't really see why COPY needs to know about
all this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-11-16 02:09:43 | Re: Parallel Seq Scan |
| Previous Message | Peter Eisentraut | 2015-11-16 01:57:51 | Re: pglogical_output - a general purpose logical decoding output plugin |