From: David Bear <David.Bear@asu.edu>
To: pgsql-admin@postgresql.org
Subject: psql copy errors
Date: Thu, 23 Jun 2005 12:27:44 -0700
Message-ID: <20050623192744.GC398@asu.edu> (raw)
I'm finding the \copy is very brittle. It seems to stop for everyone
little reason. Is there a way to tell it to be more forgiving -- for
example, to ignore extra data fields that might exists on a line?
Or, to have it just skip that offending record but continue on to the
next.
I've got a tab delimited file, but if \copy sees any extra tabs in the
file it just stops at that record. I want to be able to control what
pg does when it hits an exception.
I'm curious what others do for bulk data migration. Since copy seems
so brittle, there must be a better way...
--
David Bear
phone: 480-965-8257
fax: 480-965-9189
College of Public Programs/ASU
Wilson Hall 232
Tempe, AZ 85287-0803
"Beware the IP portfolio, everyone will be suspect of trespassing"
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: David.Bear@asu.edu
Subject: Re: psql copy errors
In-Reply-To: <20050623192744.GC398@asu.edu>
References: <20050623192744.GC398@asu.edu>
* 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