| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Simone Tellini <tellini(at)areabusiness(dot)it>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: restore whoes |
| Date: | 2002-02-11 21:29:30 |
| Message-ID: | Pine.LNX.4.30.0202111626280.1903-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tom Lane writes:
> Simple: suppose the dumped data contains \ \n in the body of a field,
> which is the currently-accepted representation for a data newline.
> Microsoft munges this to \ \r \n, which will now be read by COPY IN as a
> backslashed \r (ie, a data \r) followed by a non-escaped newline.
ISTM that this class of problem should be avoided by reading COPY input as
a text stream rather than a binary stream on all operating systems.
Doesn't that effectively guarantee that your program sees the end of the
line as "\n" only, no matter how it's actually stored?
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-11 21:34:00 | Re: restore whoes |
| Previous Message | Tom Lane | 2002-02-11 21:27:12 | Re: restore whoes |