| From: | Andrew Gould <andrewlylegould(at)gmail(dot)com> |
|---|---|
| To: | sharmi_jo(at)yahoo(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org, Sam Mason <sam(at)samason(dot)me(dot)uk> |
| Subject: | Re: Good Delimiter for copy command |
| Date: | 2009-02-12 21:15:06 |
| Message-ID: | d356c5630902121315p1ab23982h5101e0aa9de8bb31@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, Feb 12, 2009 at 2:51 PM, SHARMILA JOTHIRAJAH <sharmi_jo(at)yahoo(dot)com>wrote:
> My data fields contains commas, tabs,'|' etc. So I cant use t hem as
> delimiters..so I need a unique may be non-character to use as a delimiter...
> -Sharmila
>
How are you backing up your data? If your backup method deals appropriately
with the characters mentioned above, then backup the data and reload them
into the other tables.
If your backup method does not deal appropriately with the characters you
mention, you may have larger problems on your hands.
To the list: Does pg_dump escape characters that are the same as the
delimiter?
Thanks,
Andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SHARMILA JOTHIRAJAH | 2009-02-12 21:32:48 | Re: Good Delimiter for copy command |
| Previous Message | Raymond O'Donnell | 2009-02-12 21:11:44 | Re: Good Delimiter for copy command |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-12 21:29:38 | Re: [PERFORM] GIST versus GIN indexes for intarrays |
| Previous Message | Raymond O'Donnell | 2009-02-12 21:11:44 | Re: Good Delimiter for copy command |