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 78D6FD1B2E0 for ; Fri, 9 Jul 2004 11:22:58 -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 11558-02 for ; Fri, 9 Jul 2004 14:22:58 +0000 (GMT) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4FA06D1B190 for ; Fri, 9 Jul 2004 11:22:51 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by ucsns.ucs.co.za (Postfix) with ESMTP id 4A1AB2BDA4; Fri, 9 Jul 2004 16:22:41 +0200 (SAST) Received: from ucsns.ucs.co.za ([127.0.0.1]) by localhost (ucsns.ucs.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16764-07; Fri, 9 Jul 2004 16:22:15 +0200 (SAST) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id 2D1E92BDCE; Fri, 9 Jul 2004 16:16:48 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id 1B33FDA10B; Fri, 9 Jul 2004 16:16:48 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id EF065975A0; Fri, 9 Jul 2004 16:16:47 +0200 (SAST) Date: Fri, 9 Jul 2004 16:16:41 +0200 From: Stef To: Hilary Forbes Cc: pgsql-admin@postgresql.org Subject: Re: Bad dumps... Message-Id: <20040709161641.3e164d8f@svb.ucs.co.za> In-Reply-To: <5.1.0.14.0.20040709122158.055ac630@mailserver.dmr.co.uk> 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> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: GFoC95e6r)_TTG>n~=uFLojP=O~4W@Ms]>:.DMm/')(z3\Mwj^XP@? Q:3";lD.OM1"^mDu}2NJ@US:)dO:U*iY5EM50&Tx. X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Fri__9_Jul_2004_16_16_41_+0200_sP3yra073ddoofF4" X-Virus-Scanned: by amavisd-new at ucs.co.za 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/117 X-Sequence-Number: 14185 --Signature=_Fri__9_Jul_2004_16_16_41_+0200_sP3yra073ddoofF4 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Oops, my button doesn't work... Hilary Forbes mentioned : => Can we go back to the beginning here?! If you are doing updates to remove the \N, why are you allowing them to get into the database in the first place? Why not get rid of them in your UPDATE statement using the replace statement in the first place (or dealing with them in your source application before invoking postgres). Well, my point exactly : why can I have these values physically sitting in the database, and export successfully, but the import cannot import a successfully exported database. I have already found two other text columns where the intention was to have a value of '\N' (It is an ID code, not the null '\N'), but the values magically become null when you export and re-import the database. Also I have no control over the data in these free-hand type text columns. Users actually decided to put '\N' in there from an application, which I guess, they should feel free to do, if they want to. But it breaks backups. Kind Regards Stefan --Signature=_Fri__9_Jul_2004_16_16_41_+0200_sP3yra073ddoofF4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQCVAwUBQO6ozboLc+HYd7LFAQLeqAP+M7waH0t01t26HA83myZMvvVTQ1y6VFcx fvasjcdehQTuWlCxapqQDt2A8hTmgBCWM6NH76FgYdnA+9m534xYz+v2biZY+EBb wmE5K+6Pype2eZvZ+MBK0/1VBmphYE09keKU/7zIQLbxJrz2XRTvNY8PgpxaT7pw K52EkCTl7a0= =rHMh -----END PGP SIGNATURE----- --Signature=_Fri__9_Jul_2004_16_16_41_+0200_sP3yra073ddoofF4--