Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 7128A4762FE for ; Tue, 24 Dec 2002 10:24:46 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C468D4762D8 for ; Tue, 24 Dec 2002 10:24:45 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id gBOFOnd0019756; Tue, 24 Dec 2002 10:24:50 -0500 (EST) To: "Nikola Ivacic" Cc: pgsql-sql@postgresql.org Subject: Re: COPY command problems In-reply-to: <007d01c2ab36$85d92760$1100a8c0@rspi> References: <007d01c2ab36$85d92760$1100a8c0@rspi> Comments: In-reply-to "Nikola Ivacic" message dated "Tue, 24 Dec 2002 11:23:38 +0100" Date: Tue, 24 Dec 2002 10:24:49 -0500 Message-ID: <19755.1040743489@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/267 X-Sequence-Number: 10855 "Nikola Ivacic" writes: > Has somebody experienced difficulties using COPY command on large files. > I have a large (250MB) file and each time I insert records I've got one or = > more (< 30 of cca 1079000) corrupted > records. The number of corrupted records is not constant (i.e. 1, 30, 7, 23= > etc..) I'd bet on flaky hardware --- have you run memory and disk tests? If the COPY data is passing across a network, then network problems are also worthy of suspicion. regards, tom lane