X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D3F33D1B38A for ; Tue, 13 Jul 2004 12:40:17 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 04530-01 for ; Tue, 13 Jul 2004 15:40:16 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C9711D1B386 for ; Tue, 13 Jul 2004 12:40:12 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i6DFeC05016378; Tue, 13 Jul 2004 11:40:12 -0400 (EDT) To: Stef Cc: pgsql-admin@postgresql.org Subject: Re: Bad dumps... In-reply-to: <20040713170757.41dfc99b@svb.ucs.co.za> References: <5.1.0.14.0.20040709093611.05621ea0@mailserver.dmr.co.uk> <20040709095738.5738334f@svb.ucs.co.za> <5.1.0.14.0.20040709093611.05621ea0@mailserver.dmr.co.uk> <5.1.0.14.0.20040709122158.055ac630@mailserver.dmr.co.uk> <20040709161641.3e164d8f@svb.ucs.co.za> <1089429340.10763.10.camel@localhost.localdomain> <20040712095203.333c8aa2@svb.ucs.co.za> <20040713124000.49a556a0@svb.ucs.co.za> <15686.1089728676@sss.pgh.pa.us> <20040713170757.41dfc99b@svb.ucs.co.za> Comments: In-reply-to Stef message dated "Tue, 13 Jul 2004 17:07:57 +0200" Date: Tue, 13 Jul 2004 11:40:12 -0400 Message-ID: <16377.1089733212@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/150 X-Sequence-Number: 14218 Stef writes: > Here's what I did to recreate the problem : > ... > Welcome to psql 7.3.4, the PostgreSQL interactive terminal. Ah. I was checking it in 7.4. I thought we'd fixed this issue further back than 7.4, but some digging in the CVS logs shows not: 2003-10-05 22:38 tgl * doc/src/sgml/ref/copy.sgml, src/backend/commands/copy.c: 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. regards, tom lane