Return-Path: owner-postman
Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id KAA15199 for postgres-redist; Tue, 28 Jun 1994 10:17:36 -0700
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199406281717.KAA15199@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.149.14]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id KAA15189 for <postgres@postgres.Berkeley.EDU>; Tue, 28 Jun 1994 10:17:35 -0700
Received: from localhost (localhost [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.4/8.1B) with SMTP id KAA11377; Tue, 28 Jun 1994 10:17:01 -0700
Message-Id: <199406281717.KAA11377@faerie.CS.Berkeley.EDU>
X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost didn't use HELO protocol
From: aoki@CS.Berkeley.EDU (Paul M. Aoki)
To: joerg.plewe@mpi-dortmund.mpg.de (J.Plewe)
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: copy 
Reply-To: aoki@CS.Berkeley.EDU (Paul M. Aoki)
In-reply-to: Your message of Tue, 28 Jun 94 11:49:01 +0200 
	     <9406280949.AA10254@dl.mpi-dortmund.mpg.de> 
Date: Tue, 28 Jun 94 10:17:01 -0700
X-Sender: aoki@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
X-Mts: smtp
Resent-Date: Tue, 28 Jun 94 10:17:36 -0700
Resent-XMts: smtp

joerg.plewe@mpi-dortmund.mpg.de (J.Plewe) writes:
> When I'm using the copy-command, I have write permission to the
> postgres directory, e.g. /usr/local/postgres.
> Is this correct??
> I have no access to my own directories, because they are not
> open for postgres.

i'm not sure i understand your point.  the copy command does run as
the postgres user (since postgres does not run suid root and therefore
cannot become you) so all directories to/from which you copy must be
writable/readable by the postgres user.  also the target/source directory
will be on the server machine, not the client machine.

one could get around this by shipping everything to the frontend app
and having the client side of libpq write the file.  postgres doesn't
do that.  since the code exists for copy to/from stdout/stdin this 
wouldn't be too hard to add (in principle).
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@CS.Berkeley.EDU
                |  Berkeley, CA 94720-1776      |  ...!uunet!ucbvax!aoki

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
