Tom Lane 70e94d2dd7 Fix COPY FROM for null marker strings that correspond to invalid encoding. ... The COPY documentation says "COPY FROM matches the input against the null string before removing backslashes". It is therefore reasonable to presume that null markers like E'\\0' will work ... and they did, until someone put the tests in the wrong order during microoptimization-driven rewrites. Since then, we've been failing if the null marker is something that would de-escape to an invalidly-encoded string. Since null markers generally need to be something that can't appear in the data, this represents a nontrivial loss of functionality; surprising nobody noticed it earlier. Per report from Jeff Davis. Backpatch to 8.4 where this got broken.		2012-03-25 23:17:32 -04:00
..
examples	pgindent run for 9.0, second run	2010-07-06 19:19:02 +00:00
locale	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list	2009-06-11 14:49:15 +00:00
mb	Use diff's -w switch only on Windows, to avoid problems with inconsistent	2009-11-23 16:02:24 +00:00
performance	Add CVS tag lines to files that were lacking them.	2006-03-11 04:38:42 +00:00
regress	Fix COPY FROM for null marker strings that correspond to invalid encoding.	2012-03-25 23:17:32 -04:00
thread	Split the LDFLAGS make variable into two parts: LDFLAGS is now used for	2010-07-05 18:54:38 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00