Subject: Re: Disable copy function
To: pgsql-admin@lists.postgresql.org
References: 
 <CADzxCafS3RtPKJh1Afp0s7zvthhGXqZCgsw-p2QJVO_W3+mPrQ@mail.gmail.com>
 <8736rjlyfd.fsf@news-spur.riddles.org.uk>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <fb70b136-5fdd-b755-90ff-8d00eab0f283@gmail.com>
Date: Fri, 30 Nov 2018 03:34:12 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <8736rjlyfd.fsf@news-spur.riddles.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

On 11/30/2018 03:18 AM, Andrew Gierth wrote:
>>>>>> "prasanna" == prasanna rk <prasanna2mail@gmail.com> writes:
>   prasanna> Hi Team
>   prasanna> How do I disable copy option from database, i understand
>   prasanna> usually this option will be available only for super user,
>   prasanna> however we need to disable fully from DB.. please advice
>
> Why?

ISTM that a lot of people on this list have never worked in large companies 
run by unimaginative people who only know "Best Practice".   This crazy 
question smells of that: OP has been tasked with blocking COPY or coming 
back with an authoritative document saying why it can't be done.

> Notice that the superuser has other ways to read and write files (for
> example lo_import/lo_export, pg_read_file, using ALTER SYSTEM to
> change the log directory and filename, loading a module to call the OS,
> using file access functions in any untrusted language, etc. etc.)


-- 
Angular momentum makes the world go 'round.