Skip site navigation (1) Skip section navigation (2)

Re: out of memory problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Till Kirchner <till(dot)kirchner(at)vti(dot)bund(dot)de>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: out of memory problem
Date: 2010-11-09 15:22:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Till Kirchner <till(dot)kirchner(at)vti(dot)bund(dot)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

>        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

In response to

pgsql-performance by date

Next:From: Bob LunneyDate: 2010-11-09 16:02:42
Subject: Re: out of memory problem
Previous:From: Till KirchnerDate: 2010-11-09 10:39:48
Subject: out of memory problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group