Re: selective export for subsequent import (COPY) - Mailing list pgsql-general

From chrisj
Subject Re: selective export for subsequent import (COPY)
Date
Msg-id 10102249.post@talk.nabble.com
Whole thread Raw
In response to Re: selective export for subsequent import (COPY)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi Tom,

It appears to me that the documentation suggests that:   -P fieldsep='\t'
should work, but I don't think it does.


Tom Lane-2 wrote:
>
> chrisj <chrisj.wood@sympatico.ca> writes:
>> This helped a lot, but ideally I want a tab field delimiter and -F '\t'
>> does
>> not seem to work, any ideas??
>
> I don't think there's any provision for backslash-notation in that
> switch; you'd need to type an actual tab character there.  Depending on
> what shell you use, that might be a bit difficult on an interactive
> shell command line, but it should be simple enough to insert one in a
> script file.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>

--
View this message in context:
http://www.nabble.com/selective-export-for-subsequent-import-%28COPY%29-tf3604927.html#a10102249
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: marcelo Cortez
Date:
Subject: nedd help bytea encode
Next
From: Tom Lane
Date:
Subject: Re: cant get pg_dump/pg_restore to behave