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-17 00:10:17 |
Message-ID: | AANLkTinWvV3-MpK3Qumc2z=g=rWWScjgCN1Tb_wyDw5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Nov 17, 2010 at 1:00 AM, 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:
>> Well, the query works if executed in psql client. Seems to be a Python
>> problem. I'll execute the rest of the loop queries in the client, just
>> in case.
>
>> But in case is a Python problem, why does it affect the postgres
>> process, causing a crash?
>
> Is the query parameterized when issued from Python? If so it might work
> differently.
>
> regards, tom lane
>
Yes, it takes the table names from another query (select table_names
from other_table), and the fields names from a XML file. Can the query
which fetch the table names cause a memory problem? Seems weird
--
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-17 00:13:28 | Re: Programming error: Out of Memory |
Previous Message | Tom Lane | 2010-11-17 00:00:18 | Re: Programming error: Out of Memory |