From: Stef <svb@ucs.co.za>
To: pgsql-admin@postgresql.org
Subject: Bad dumps...
Date: Fri, 9 Jul 2004 09:57:38 +0200
Message-ID: <20040709095738.5738334f@svb.ucs.co.za> (raw)
Hi all,
I'm stuck with a problem,about which I couldn't find
much info. I'm sure somebody must have encountered this before.
I've got a "NOT NULL" column of type text.
It happens that freehand data gets inserted into this table, and
it typically contains over 1000 rows with the value '\N' , and
about another 3400 rows that has an occurrence of '\N'
The database dumps fine, but when I import it again, I get
"cannot insert null value into not null column"-type errors,
and if I don't pay close attention, I end up with an empty table
on the database. There is no way for me to tell how many columns
could be affected in future, but I need to stabilize the backups.
I'm using postgres version 7.3.4
Any idea how to get around this problem?
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: svb@ucs.co.za
Subject: Re: Bad dumps...
In-Reply-To: <20040709095738.5738334f@svb.ucs.co.za>
References: <20040709095738.5738334f@svb.ucs.co.za>
* 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