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

From chrisj
Subject Re: selective export for subsequent import (COPY)
Date
Msg-id 10139682.post@talk.nabble.com
Whole thread Raw
In response to Re: selective export for subsequent import (COPY)  (Andrew Kroeger <andrew@sprocks.gotdns.com>)
Responses Re: selective export for subsequent import (COPY)
List pgsql-general
Wow, how did you discover that?


Andrew Kroeger wrote:
>
> Tom Lane 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.
>
> I'm not sure what shell is being used, but the following works with
> bash, csh, tcsh, and ksh under Linux:
>
> In order to emit an actual tab character on the shell command line (and
> ignore any shell auto-completion features that are normally tied to the
> tab key), preface the literal tab character with Ctrl-V.  Thus, the
> delimiter specification from above would be typed "-F '<Ctrl-V><Tab>'".
>
> Hope this helps.
>
> Andrew
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
>
>

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


pgsql-general by date:

Previous
From: Andrew Kroeger
Date:
Subject: Re: selective export for subsequent import (COPY)
Next
From: Karsten Hilbert
Date:
Subject: Re: dollar-quoting trouble