Re: pg_dump output

From: Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump output
Date: 2001-02-12 19:10:09
Message-ID: Pine.LNX.4.21.0102122008020.11070-100000@pc10.radnoti-szeged.sulinet.hu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 12 Feb 2001, Peter Eisentraut wrote:

> Kovacs Zoltan writes:
>
> > In 7.0.2 I got
> > INSERT INTO foo (field) VALUES ('Hello,\012world!');
>
> > In 7.1beta4 I get
> > INSERT INTO foo (field) VALUES ('Hello,
> > world!');
>
> > Is it possible to add a switch to pg_dump to make it possible getting the
> > old output. Where can I balance it in the source if I'd like to change the
> > behaviour?
>
> I kind of agree that the old output should be preferred. Otherwise we
> might be entering a whole new world of CR/LF sort of problems.
>
> Btw., if I select the default COPY output, pg_dump seems to drop
> non-printable characters like '\001'.
OK, I found it. In pg_dump.c, function formatStringLiteral(), the line
containing '\n' and '\t' should be deleted (or check whether a switch is
on or not).

Zoltan
--
Kov\'acs, Zolt\'an
kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu
http://www.math.u-szeged.hu/~kovzol
ftp://pc10.radnoti-szeged.sulinet.hu/home/kovacsz

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-12 20:13:37 Re: pg_dump output
Previous Message Peter Eisentraut 2001-02-12 18:24:33 Re: pg_dump output