From: Gavin Sherry <swm@alcove.com.au>
To: Steven Rosenstein <srosenst@us.ibm.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Bulk COPY end of copy delimiter
Date: Tue, 5 Apr 2005 10:00:15 +1000 (EST)
Message-ID: <Pine.LNX.4.58.0504050952410.20850@linuxworld.com.au> (raw)
In-Reply-To: <OF93689C76.0D3B597A-ON85256FD9.0081921E-85256FD9.00820D37@us.ibm.com>
References: <OF93689C76.0D3B597A-ON85256FD9.0081921E-85256FD9.00820D37@us.ibm.com>
Hi,
On Mon, 4 Apr 2005, Steven Rosenstein wrote:
>
>
>
>
> Today while trying to do a bulk COPY of data into a table, the process
> aborted with the following error message:
>
> ERROR: end-of-copy marker corrupt
> CONTEXT: COPY tbl_logged_event, line 178519: "606447014,1492,2005-02-24
> 03:16:14,2005-02-23 20:27:48,win_applog,,error,adsmclientservice,nt
> author..."
>
> Googling the error, we found reference to the '\.' (backslash-period) being
> an "end-of-copy marker". Unfortunately, our data contains the
> backslash-period character sequence. Is there any know fix or workaround
> for this condition?
Any sequence \. in COPY input data should be escaped as \\. If this data
was generated by pg_dump then its a problem, but I haven't seen any other
reports of this. Can I assume that you've generated the data for bulk load
yourself? If so, there is discussion of escaping characters here:
http://www.postgresql.org/docs/8.0/static/sql-copy.html.
Gavin
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-performance@postgresql.org
Cc: swm@alcove.com.au, srosenst@us.ibm.com
Subject: Re: Bulk COPY end of copy delimiter
In-Reply-To: <Pine.LNX.4.58.0504050952410.20850@linuxworld.com.au>
* 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