From: | Jorge Arévalo <jorge(dot)arevalo(at)deimos-space(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Programming error: Out of Memory |
Date: | 2010-11-16 23:02:08 |
Message-ID: | AANLkTi=YTj_MaJq-zU9mzJLXHHXsy0T7am2wR5bC3gTw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Nov 16, 2010 at 11:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?ISO-8859-1?Q?Jorge_Ar=E9valo?= <jorge(dot)arevalo(at)deimos-space(dot)com> writes:
>> I'm getting an error message in my Python script:
>
>> pg.ProgrammingError: ERROR: out of memory
>> DETAIL: Failed on request of size 16.
>
> That's pretty odd because the memory map you provided isn't showing any
> particular signs of bloat. I wonder whether either Python or PostGIS
> is leaking memory directly (ie, through malloc calls, which wouldn't
> show in the memory map).
>
> Can you boil it down to a self-contained test case?
>
> regards, tom lane
>
Before executing the queries, the app reads a small XML file, to get
names and paths, basically. I could simply execute the query in the
console client, to isolate it. Would it be enough?
Just now I'm testing what happens if I add vm.overcommit_memory=2 to
sysctl.conf, and execute sysctl -p. If crashes again, I'll isolate the
query
Thanks again
--
Jorge Arévalo
Internet & Mobilty Division, DEIMOS
jorge(dot)arevalo(at)deimos-space(dot)com
http://mobility.grupodeimos.com/
http://gis4free.wordpress.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-16 23:11:14 | Re: AfterTriggerSaveEvent() called outside of query |
Previous Message | Elliot Chance | 2010-11-16 23:00:25 | Re: Postgres forums ... take 2 |