From: mike g <mike@thegodshalls.com>
To: Stef <svb@ucs.co.za>
Cc: Hilary Forbes <hforbes@dmr.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bad dumps...
Date: Fri, 09 Jul 2004 22:15:41 -0500
Message-ID: <1089429340.10763.10.camel@localhost.localdomain> (raw)
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>
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 <Reply all> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mike@thegodshalls.com, svb@ucs.co.za, hforbes@dmr.co.uk
Subject: Re: Bad dumps...
In-Reply-To: <1089429340.10763.10.camel@localhost.localdomain>
References: <5.1.0.14.0.20040709093611.05621ea0@mailserver.dmr.co.uk> <20040709095738.5738334f@svb.ucs.co.za> <5.1.0.14.0.20040709122158.055ac630@mailserver.dmr.co.uk> <20040709161641.3e164d8f@svb.ucs.co.za> <1089429340.10763.10.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox