From: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Problem with COPY in 8.0.3 |
Date: | 2005-10-12 18:08:20 |
Message-ID: | 1129140500.6751.223.camel@linda.lfix.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, 2005-10-12 at 13:52 -0400, Tom Lane wrote:
> Oliver Elphick <olly(at)bray-healthcare(dot)com> writes:
> > Pg 8.0.3 (Debian package) on AMD64, linux 2.6.12
> > I am importing a table using COPY. The data is tab-delimited. COPY
> > seems to be putting the data for one field into the preceding field,
> > which should contain the empty string.
>
> Can't reproduce that here, under either 8.0 or CVS tip. Are you sure
> you aren't making some silly mistake, like copying from the wrong file?
No. This is a regular (nightly) scripted dump, which drops and rebuilds
the entire database, and the right data is going into the file (I only
showed one line out of 300+). But in this particular case, the column
order was wrong. I should add that the table inherits from another one,
but the swapped columns are a long way into the extra columns specific
to this table.
I've changed the script to fix it, so its not a big issue for me, but I
first noticed it several days ago, so it's not a one off occurrence.
Oliver
--
Oliver Elphick olly(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA
========================================
Do you want to know God? http://www.lfix.co.uk/knowing_god.html
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-10-12 18:13:34 | Re: Problem with COPY in 8.0.3 |
Previous Message | Tom Lane | 2005-10-12 17:52:35 | Re: Problem with COPY in 8.0.3 |