Re: (no subject)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "A(dot) Van Hook" <hook(at)kcp(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: (no subject)
Date: 2003-08-07 15:10:32
Message-ID: 15671.1060269032@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

"A. Van Hook" <hook(at)kcp(dot)com> writes:
> Dump files are used to restore and test. This test method has been used
> successfully on
> all previous versions. However, in 7.3.3, when the dump utility hits a
> carriage return imbeded with in a text field, the
> dump utility immeadiately jumps to the next record rendering the dump of
> successive records useless.

AFAICT, pg_dump with -D in 7.3 and current dumps embedded carriage
returns and newlines literally, same as it always has. I suspect your
problems are not actually with Postgres, but with some other tool that
is misreading or altering the dump file.

Personally, I would use pg_dump without -D. Recent versions give a
fairly nice behavior for embedded control characters:

COPY foo (f1) FROM stdin;
aaa\rbbb\r\nccc
aaa\rbbb\r\nccc
\.

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Robert Treat 2003-08-07 15:43:42 Re: [GENERAL] Postgresql slow on XEON 2.4ghz/1gb ram
Previous Message A. Van Hook 2003-08-07 10:14:16 (no subject)