From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | dinesh kumar <dineshkumar02(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposing COPY .. WITH PERMISSIVE |
Date: | 2015-07-23 16:21:09 |
Message-ID: | CA+TgmoYYLUuoVV5EF9xdYo6SosngJ7zk2nBN1v=uCCfgVL9zpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 23, 2015 at 12:19 PM, dinesh kumar <dineshkumar02(at)gmail(dot)com> wrote:
> Sorry for my unclear description about the proposal.
>
> "WITH PERMISSIVE" is equal to our existing behavior. That is, chmod=644 on
> the created files.
>
> If User don't specify "PERMISSIVE" as an option, then the chmod=600 on
> created files. In this way, we can restrict the other users from reading
> these files.
There might be some benefit in allowing the user to choose the
permissions, but (1) I doubt we want to change the default behavior
and (2) providing only two options doesn't seem flexible enough.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2015-07-23 16:43:57 | Re: All-zero page in GIN index causes assertion failure |
Previous Message | Robert Haas | 2015-07-23 16:20:01 | Re: pgbench stats per script & other stuff |