Re: PG 7.4 beta 2: COPY IN, arrays, and double quotes bug. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: PG 7.4 beta 2: COPY IN, arrays, and double quotes bug.
Date
Msg-id 680.1063175941@sss.pgh.pa.us
Whole thread Raw
In response to PG 7.4 beta 2: COPY IN, arrays, and double quotes bug.  (Bertrand Petit <pgsql-bugs@phoe.frmug.org>)
List pgsql-bugs
Bertrand Petit <pgsql-bugs@phoe.frmug.org> writes:
> One of the attribs value is piped to the backend as {"3/4\""}, this is
> how the array appears on the wire, and PG rejected it with the
> following message, as submited to syslog:

> postgres[90257]: [51-1] ERROR:  malformed array literal: "{"3/4""}"

Seems like a client-side quoting bug to me.  Backslashes have to be
doubled at the sending end, because COPY itself will do one level of
backslash processing.

If the client-side code is ours, then it's our problem, but you did not
say what you are using...

> P.S.: despites that this PG vresion was CVS updated after the release
> of beta 2, it still identifies itself as beta1:

Sounds like you didn't re-run configure after updating.  I doubt that
affects the COPY issue above, but it surely might cause some other
problems.  My invariable procedure for updating from CVS is a complete
rebuild:
        make distclean
        cvs update
        configure
        make
This costs a few machine cycles but I figure that's cheap compared to my
time puzzling out meaningless failures.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: [GENERAL] plPGSQL bug in function creation
Next
From: Torello Querci
Date:
Subject: Date 1973/06/03 Conversion Problem in 7.3.4 and 7.3.2.