From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Creager, Robert S" <CreagRS(at)LOUISVILLE(dot)STORTEK(dot)COM> |
Cc: | "'General - PGSQL'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: COPY problem |
Date: | 2001-03-10 03:14:42 |
Message-ID: | 13462.984194082@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Creager, Robert S" <CreagRS(at)LOUISVILLE(dot)STORTEK(dot)COM> writes:
> What I've done is copy the original table into a file, and am now attempting
> to copy from stdin, using Perl/Pg to break out the data into the 6 tables.
> I'm working with 2.5 million records btw. I've narrowed the situation to
> occur when copying to any one of the 5 referring tables (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).
Ah, another memory leak that's yet un-plugged. Can you gin up a
self-contained example that reproduces the leak? Should be fixable
if we can figure out exactly where the leak is occurring.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Marschalek | 2001-03-10 03:19:54 | Question |
Previous Message | Erik Tennant | 2001-03-10 03:04:05 | JRelationalFramework |