Re: Transaction eating up all RAM - Mailing list pgsql-general

From Tom Lane
Subject Re: Transaction eating up all RAM
Date
Msg-id 9033.1142275499@sss.pgh.pa.us
Whole thread Raw
In response to Re: Transaction eating up all RAM  ("Peter" <peter@greatnowhere.com>)
List pgsql-general
"Peter" <peter@greatnowhere.com> writes:
> I have no triggers defined on any of the tables, and no foreign keys that
> could cause cascaded updates and stuff. Care to see full text of the proc?
> It's pl/PgPerlU

If there's no triggers involved then it sounds like a memory leak.  What
PG version is this?  If it's current then we'd like a test case, yes.

            regards, tom lane

pgsql-general by date:

Previous
From: Greg Stark
Date:
Subject: Re: Wal -long transaction
Next
From: Tom Lane
Date:
Subject: Re: ERROR: FULL JOIN is only supported with merge-joinable