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 6FCCED1B26E for ; Sat, 10 Jul 2004 00:17:11 -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 29111-07 for ; Sat, 10 Jul 2004 03:17:08 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by svr1.postgresql.org (Postfix) with ESMTP id 4A4F8D1B23F for ; Sat, 10 Jul 2004 00:17:01 -0300 (ADT) Received: from localhost.localdomain (c-67-162-89-61.client.comcast.net[67.162.89.61]) by comcast.net (rwcrmhc13) with ESMTP id <2004071003170501500hspkde>; Sat, 10 Jul 2004 03:17:06 +0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i6A3Fgtr010853; Fri, 9 Jul 2004 22:15:42 -0500 Received: (from spike@localhost) by localhost.localdomain (8.12.11/8.12.11/Submit) id i6A3FfTI010850; Fri, 9 Jul 2004 22:15:41 -0500 X-Authentication-Warning: localhost.localdomain: spike set sender to mike@thegodshalls.com using -f Subject: Re: Bad dumps... From: mike g Reply-To: mike@thegodshalls.com To: Stef Cc: Hilary Forbes , pgsql-admin@postgresql.org In-Reply-To: <20040709161641.3e164d8f@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> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1089429340.10763.10.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Fri, 09 Jul 2004 22:15:41 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/125 X-Sequence-Number: 14193 That could be a bug. How are you dumping the data? pg_dump? Select query? How are you restoring the data? psql? On Fri, 2004-07-09 at 09:16, Stef wrote: > 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