| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to stop script executions |
| Date: | 2016-07-26 14:19:09 |
| Message-ID: | CAKFQuwb32eBEEc=CthxA+TxJkFVn2Ekdg9n2OvE-sK4qAt13MA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jul 26, 2016 at 9:48 AM, Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> wrote:
> On Tue, Jul 26, 2016 at 6:54 PM, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> Superuser: yes (specifically I'm thinking the COPY FROM PROGRAM command,
>> but also C language functions)
>> Ordinary user: not that I can think of.
>>
>
> OK, is there a way to restrict usage of COPY FROM PROGRAM command?
>
>
For superusers, no. You'd have to protect the system using external tools
to limit what areas and commands the postgres (or whatever PostgreSQL runs
as) user can access.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John McKown | 2016-07-26 14:23:15 | Re: How to stop script executions |
| Previous Message | Melvin Davidson | 2016-07-26 14:05:04 | Re: How to stop script executions |