From: Tom Lane <tgl@sss.pgh.pa.us>
To: A. Van Hook <hook@kcp.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: (no subject)
Date: Thu, 07 Aug 2003 11:10:32 -0400
Message-ID: <15671.1060269032@sss.pgh.pa.us> (raw)
In-Reply-To: <3F322678.5070908@kcp.com>
References: <3F322678.5070908@kcp.com>
"A. Van Hook" <hook@kcp.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
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, hook@kcp.com
Subject: Re: (no subject)
In-Reply-To: <15671.1060269032@sss.pgh.pa.us>
* 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