Re: COPY fast parse patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Alon Goldshuv <agoldshuv(at)greenplum(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY fast parse patch
Date: 2005-06-02 01:20:06
Message-ID: 200506020120.j521K6U05680@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Alon Goldshuv wrote:
> 5) Data integrity and escaping improvements. Treats all characters as data
> (unless it's an escaped delim or EOL) and therefore data
> integrity is preserved. However, some people that already got
> used to the postgres COPY escaping way may want to keep it. They could do so
> by still using the old COPY.

OK, if the COPY file contains:

\n\||\r\\a|\N

and the delimiter is '|', what does that represent? What if there were
a literal '\' followed by a '|' in the data table being dumped?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-06-02 01:24:11 Re: [PATCHES] Adding \x escape processing to COPY, psql, backend
Previous Message Christopher Kings-Lynne 2005-06-02 01:04:03 Re: patch for between symmetric, asymmetric (from TODO)