RE: COPY problem

From: "Creager, Robert S" <CreagRS(at)LOUISVILLE(dot)STORTEK(dot)COM>
To: "'Gordon A(dot) Runkle'" <gar(at)no-spam-integrated-dynamics(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: RE: COPY problem
Date: 2001-03-13 01:31:05
Message-ID: 10FE17AD5F7ED31188CE002048406DE8514CF9@lsv-msg06.stortek.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Tom believes there may be a memory leak, which would be causing the
(strangely enough) memory problem. Didn't think about reducing the import
size. What I might try in that case would be to re-connect to the db
periodically, rather than splitting the file. The problem becomes
unmanageable after around 15000 entries, so splitting 2.5M lines wouldn't be
pleasant (167 files).

Thanks,
Rob

Robert Creager
Senior Software Engineer
Client Server Library
303.673.2365 V
303.661.5379 F
888.912.4458 P
StorageTek
INFORMATION made POWERFUL

> -----Original Message-----
> From: Gordon A. Runkle [mailto:gar(at)no-spam-integrated-dynamics(dot)com]
> Sent: Friday, March 09, 2001 7:18 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] COPY problem
>
> I can't answer the backend question, but how about running
> 'split' on the big file, then COPYing these smaller files?
>
> Gordon.
>

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-03-13 01:52:19 Re: socket file must reside in /tmp?
Previous Message tc lewis 2001-03-13 01:26:51 socket file must reside in /tmp?