Search Postgresql Archives

linux bug and lost rows

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A long time ago I wrote to the list about a problem I was having with COPY losing rows from an import file: the number of imported rows was not equal to the number of rows in the file, and two consecutive imports from the same file would get different row counts. Several people tried to reproduce it unsuccessfully. Reference: http://archives.postgresql.org/pgsql-general/2006-07/msg00925.php

More recently, as I was practicing a database upgrade to 8.2.3, I captured an "unexpected data beyond EOF" in the log, which led to missing tables in the upgraded db. I opened a thread, and it turned out someone had previously had the same problem, and it was due to the Linux kernel version: 2.6.5-7.244
Reference: http://archives.postgresql.org/pgsql-general/2007-03/msg01543.php

Now my server has been upgraded to 2.6.5-7.282, and I'm happy to report that BOTH problems have disappeared. The first problem, that of lost rows for COPY, tended to present itself for large import files, nearing 1GB, but I was never able to get reproducible results. As I understand, the Linux bug responsible for the "unexpected data beyond EOF" had to do with faulty disk reads. Probably this was also affecting the COPY command, only failing silently?


***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.

Bear Stearns does not provide tax, legal or accounting advice.  You
should consult your own tax, legal and accounting advisors before
engaging in any transaction. In order for Bear Stearns to comply with
Internal Revenue Service Circular 230 (if applicable), you are notified
that any discussion of U.S. federal tax issues contained or referred to
herein is not intended or written to be used, and cannot be used, for
the purpose of:  (A) avoiding penalties that may be imposed under the
Internal Revenue Code; nor (B) promoting, marketing or recommending to
another party any transaction or matter addressed herein.
***********************************************************************


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux