Re: COPY problem

From: "Gordon A(dot) Runkle" <gar(at)no-spam-integrated-dynamics(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: COPY problem
Date: 2001-03-10 02:18:28
Message-ID: 98c2r3$13uc$1@news.tht.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In article <10FE17AD5F7ED31188CE002048406DE8514CEE(at)lsv-msg06(dot)stortek(dot)com>,
"Creager, Robert S" <CreagRS(at)louisville(dot)stortek(dot)com> wrote:

> I think this is a question regarding the backend, but...

[snip]

> (COPY u FROM stdin). The backend process which handles the db connection
> decides that it needs a whole lot of memory, although in a nice
> controlled manner. The backend starts with using 6.5Mb, and at 25000
> records copied, it's taken 10Mb and has slowed down substantially.
> Needless to say, this COPY will not finish before running out of memory
> (estimated 300Mb). When executing the COPY to the loc table, this
> problem does not occur. Am I going to have to resort to inserts for the
> referring tables?

I can't answer the backend question, but how about running
'split' on the big file, then COPYing these smaller files?

Gordon.

--
It doesn't get any easier, you just go faster.
-- Greg LeMond

In response to

  • COPY problem at 2001-03-09 21:34:40 from Creager, Robert S

Browse pgsql-general by date

  From Date Subject
Next Message Erik Tennant 2001-03-10 03:04:05 JRelationalFramework
Previous Message Marc Wrubleski 2001-03-10 02:18:00 Determine Time in other Time Zone