From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jon Clements <jon.clements@trgstrata.co.uk>
Cc: pgsql-interfaces@postgresql.org <pgsql-interfaces@postgresql.org>
Subject: Re: PLPythonU & Out of Memory - Importing Query
Date: Wed, 09 Nov 2005 11:52:35 -0500
Message-ID: <16566.1131555155@sss.pgh.pa.us> (raw)
In-Reply-To: <4c05f1b439ce248766e7cd5375a83ddc@readgroup.co.uk>
References: <4c05f1b439ce248766e7cd5375a83ddc@readgroup.co.uk>
Jon Clements <jon.clements@trgstrata.co.uk> writes:
> I am currently experimenting using plpythonu with postgresql 8.0 for
> Win32. It's basically a quick script that imports data from CSV files,
> but does some quite complicated data lookups and selections. The area
> in which I'm somewhat confunded is memory usage. The process
> successfully runs, but keeps climbing in memory usage relentlessly,
> successfully importing about 200k records, before the memory usage of
> postgres soars to 2gb and of course, shortly after that, grinds to a
> halt with a "Out of Memory" error.
You may have stumbled across a memory leak in plpythonu, but there's
not enough info here for anyone to investigate. Can you put together
a self-contained test case for people to try?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, jon.clements@trgstrata.co.uk
Subject: Re: PLPythonU & Out of Memory - Importing Query
In-Reply-To: <16566.1131555155@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox