Re: [HACKERS] memory problem again - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] memory problem again
Date
Msg-id 20747.944531606@sss.pgh.pa.us
Whole thread Raw
In response to memory problem again  (Daniel Kalchev <daniel@digsys.bg>)
Responses Re: [HACKERS] memory problem again
(resolution?) Re: [HACKERS] memory problem again
List pgsql-hackers
Daniel Kalchev <daniel@digsys.bg> writes:
> I have this problem with PostgreSQL 6.5.2:

> logs=> select distinct confid 
> logs-> from timelog199910
> logs-> where
> logs-> confid IS NOT NULL;
> pqReadData() -- backend closed the channel unexpectedly.

> The logged message in stderr (of postmaster) is 
> FATAL 1:  Memory exhausted in AllocSetAlloc()

Odd.  I can't replicate this here.  (I'm using 6.5.3, but I doubt that
matters.)  There must be some factor involved that you haven't told us.
You don't have any triggers or rules on the table, do you?

Has anyone else seen anything like this?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Raising funds for PostgreSQL
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] When is 7.0 going Beta?