FATAL ERROR running query...

Started by Ligia Pimentelalmost 25 years ago3 messagesgeneral
Jump to latest
#1Ligia Pimentel
lmpimentel@yahoo.com

I have a problem with postgres, I'm running a query that joins two tables,
one with 129000+ records, and the other with 1172 records, it's a very
simple join. But postgres can't handle it!!! (Both tables have an index on
the field "cuentacb").

I get the following error after 3 minutes...

migracion=# select * from cuentasequivalentes, equiv11mayo m
migracion-# where cuentasequivalentes.cuentacb = m.cuentacb
migracion-# and cuentasequivalentes.cuentabr <> m.cuentabr;
FATAL 1: Memory exhausted in AllocSetAlloc()
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.

What can I do? I'm guessing that I could change a configuration parameter or
something like that, but I don't know.

Please help me, it's kind of urgent.

Ligia

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Ligia Pimentel (#1)
Re: FATAL ERROR running query...

"Ligia Pimentel" <lmpimentel@yahoo.com> writes:

I get the following error after 3 minutes...
FATAL 1: Memory exhausted in AllocSetAlloc()
What can I do?

Update to PG 7.1. It's a lot better about not leaking memory.

regards, tom lane

#3Ligia Pimentel
lmpimentel@yahoo.com
In reply to: Tom Lane (#2)
Re: FATAL ERROR running query...

Thank you. It's better now.

"Tom Lane" <tgl@sss.pgh.pa.us> wrote in message
news:26418.989884157@sss.pgh.pa.us...

Show quoted text

"Ligia Pimentel" <lmpimentel@yahoo.com> writes:

I get the following error after 3 minutes...
FATAL 1: Memory exhausted in AllocSetAlloc()
What can I do?

Update to PG 7.1. It's a lot better about not leaking memory.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org