From: Tom Lane <tgl@sss.pgh.pa.us>
To: Till Kirchner <till.kirchner@vti.bund.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: out of memory problem
Date: Tue, 09 Nov 2010 10:22:33 -0500
Message-ID: <17966.1289316153@sss.pgh.pa.us> (raw)
In-Reply-To: <4CD924F4.6000607@vti.bund.de>
References: <4CD924F4.6000607@vti.bund.de>
Till Kirchner <till.kirchner@vti.bund.de> writes:
> I get an out of memory problem I don't understand.
It's pretty clear that something is leaking memory in the per-query
context:
> ExecutorState: 1833967692 total in 230 blocks; 9008 free (3
> chunks); 1833958684 used
There doesn't seem to be anything in your query that is known to cause
that sort of thing, so I'm guessing that the leak is being caused by
the postgis functions you're using. You might ask about this on the
postgis lists.
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, till.kirchner@vti.bund.de
Subject: Re: out of memory problem
In-Reply-To: <17966.1289316153@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