pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Possible TODO item: copy to/from pipe
Date: 04 Jun 2006 17:39:17 -0400
Message-ID: <87hd30bny2.fsf@stark.xeocode.com> (raw)
In-Reply-To: <4482CCE5.6020900@pse-consulting.de>
References: <200606040012.k540C5V29587@candle.pha.pa.us>
	<4482CCE5.6020900@pse-consulting.de>

Andreas Pflug <pgadmin@pse-consulting.de> writes:

> Bruce Momjian wrote:
> >
> > For use case, consider this:
> >
> >  	COPY mytable TO '| rsh x@y.com > test ';
> >
> > so you can COPY to another server directly.
> >
> Why not rsh psql -c "\copy foobar to test" ?

Who knows? The sysadmin could have any reason to prefer one to the other. 

One that comes to mind is that he or she may want to automate this and may be
happier granting password-free access to a filesystem server that just holds
encrypted backups than to the live production database.

-- 
greg




view thread (36+ messages)

Message-ID: <87hd30bny2.fsf@stark.xeocode.com>
Permalink:  ../87hd30bny2.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87hd30bny2.fsf@stark.xeocode.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: gsstark@mit.edu, pgadmin@pse-consulting.de, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us
  Subject: Re: Possible TODO item: copy to/from pipe
  In-Reply-To: <87hd30bny2.fsf@stark.xeocode.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox