On Wed, Nov 17, 2010 at 1:13 AM, Tom Lane wrote:
> =?ISO-8859-1?Q?Jorge_Ar=E9valo?= writes:
>> 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? Seem
=?ISO-8859-1?Q?Jorge_Ar=E9valo?= writes:
> 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
Well, we were already in pretty-weird territor
On Wed, Nov 17, 2010 at 1:00 AM, Tom Lane wrote:
> =?ISO-8859-1?Q?Jorge_Ar=E9valo?= 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 doe
=?ISO-8859-1?Q?Jorge_Ar=E9valo?= 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
2010/11/17 Jorge Arévalo :
> On Wed, Nov 17, 2010 at 12:14 AM, Tom Lane wrote:
>> =?ISO-8859-1?Q?Jorge_Ar=E9valo?= writes:
>>> On Tue, Nov 16, 2010 at 11:46 PM, Tom Lane wrote:
Can you boil it down to a self-contained test case?
>>
>>> Before executing the queries, the app reads a small XML
On Wed, Nov 17, 2010 at 12:14 AM, Tom Lane wrote:
> =?ISO-8859-1?Q?Jorge_Ar=E9valo?= writes:
>> On Tue, Nov 16, 2010 at 11:46 PM, Tom Lane wrote:
>>> Can you boil it down to a self-contained test case?
>
>> Before executing the queries, the app reads a small XML file, to get
>> names and paths,
=?ISO-8859-1?Q?Jorge_Ar=E9valo?= writes:
> On Tue, Nov 16, 2010 at 11:46 PM, Tom Lane wrote:
>> Can you boil it down to a self-contained test case?
> 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
> conso
On Tue, Nov 16, 2010 at 11:46 PM, Tom Lane wrote:
> =?ISO-8859-1?Q?Jorge_Ar=E9valo?= 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
=?ISO-8859-1?Q?Jorge_Ar=E9valo?= 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
2010/11/16 Andy Colson :
> On 11/16/2010 3:55 PM, Jorge Arévalo wrote:
>>
>> Hello,
>>
>> I'm getting an error message in my Python script:
>>
>> pg.ProgrammingError: ERROR: out of memory
>> DETAIL: Failed on request of size 16.
>>
>> The query that caused the error was:
>>
>> UPDATE table1 SET s
On 11/16/2010 3:55 PM, Jorge Arévalo wrote:
Hello,
I'm getting an error message in my Python script:
pg.ProgrammingError: ERROR: out of memory
DETAIL: Failed on request of size 16.
The query that caused the error was:
UPDATE table1 SET string = (SELECT string FROM table2 WHERE
ST_Centroid(t
Hello,
I'm getting an error message in my Python script:
pg.ProgrammingError: ERROR: out of memory
DETAIL: Failed on request of size 16.
The query that caused the error was:
UPDATE table1 SET string = (SELECT string FROM table2 WHERE
ST_Centroid(table1.wkb_geometry) && table2. the_geom AND
(S
12 matches
Mail list logo
