From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Silvela, Jaime \(Exchange\)" <JSilvela(at)Bear(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: copy losing information |
Date: | 2006-09-26 15:15:08 |
Message-ID: | 25944.1159283708@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Silvela, Jaime \(Exchange\)" <JSilvela(at)Bear(dot)com> writes:
> I have a pretty big file, around 2 million rows, in tab-separated
> format, with 4 columns, that I read into a table in Postgres using the
> copy command.
> I've started to notice missing info sometimes. I'll truncate the table,
> read from the file, and notice that sometimes there are less rows in the
> table than in the file.
This looks a lot like Dan Kavan's problem,
http://archives.postgresql.org/pgsql-admin/2006-09/msg00092.php
which we have now pretty well proven was a kernel bug.
> The version running in the server is 8.1.3 on Linux 2.6.5 on an Intel
> platform.
2.6.5 what exactly? And what's the "Intel platform"? Although I don't
have any details about the kernel bug, I can't help suspecting that it
only manifested on systems pretty similar to Dan's dual Opteron.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brandon Aiken | 2006-09-26 15:32:21 | Re: change the order of FROM selection to make query work |
Previous Message | Brandon Aiken | 2006-09-26 14:58:26 | Re: serial column |