RE: COPY problem

Поиск
Список
Период
Сортировка
От Creager, Robert S
Тема RE: COPY problem
Дата
Msg-id 10FE17AD5F7ED31188CE002048406DE8514CF9@lsv-msg06.stortek.com
обсуждение исходный текст
Ответ на COPY problem  ("Creager, Robert S" <CreagRS@LOUISVILLE.STORTEK.COM>)
Список 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@no-spam-integrated-dynamics.com]
> Sent: Friday, March 09, 2001 7:18 PM
> To: pgsql-general@postgresql.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.
>

В списке pgsql-general по дате отправления:

Предыдущее
От: tc lewis
Дата:
Сообщение: socket file must reside in /tmp?
Следующее
От: "Scott Price"
Дата:
Сообщение: pqReadData() - backend unexpectedly closed the channel