Skip site navigation (1) Skip section navigation (2)

Re: pgsql-server/ oc/src/sgml/ref/copy.sgml rc/bac ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server/ oc/src/sgml/ref/copy.sgml rc/bac ...
Date: 2003-10-06 04:02:45
Message-ID: 19334.1065412965@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Neil Conway <neilc(at)samurai(dot)com> writes:
> On Sun, 2003-10-05 at 22:38, Tom Lane wrote:
>> Modify COPY FROM to match the null-value string against the column value
>> before it is de-backslashed, not after.  This allows the null string \N
>> to be reliably distinguished from the data value \N (which must be
>> represented as \\N).  Per bug report from Manfred Koizar ... but it's
>> amazing this hasn't been reported before ...
>> Also, be consistent about encoding conversion for null string: the form
>> specified in the command is in the server encoding, but what is sent
>> to/from client must be in client encoding.  This never worked quite
>> right before either.

> Should either of these be backpatched to 7.3?

It was a minor change given previous hacking on 7.4, but I don't see any
simple way to backpatch to 7.3.  We'd have to backport some nontrivial
changes that (IMHO) aren't well enough proven yet.  So even though there
is clearly a bug here, it's a bug that's escaped detection for N years,
and so I'm not eager to risk introducing other bugs in order to squash
it.

Once the fixed code has undergone some field testing I'd be willing to
backpatch it, but by then the issue may be moot ...

			regards, tom lane

In response to

Responses

pgsql-committers by date

Next:From: Neil ConwayDate: 2003-10-06 04:09:21
Subject: Re: pgsql-server/ oc/src/sgml/ref/copy.sgml rc/bac ...
Previous:From: Neil ConwayDate: 2003-10-06 03:34:03
Subject: Re: pgsql-server/ oc/src/sgml/ref/copy.sgml rc/bac ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group