From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org (PostgreSQL HACKERS) |
Subject: | Re: [HACKERS] Memory not freed at WARN |
Date: | 1998-02-25 17:54:56 |
Message-ID: | m0y7l2n-000BFRC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On October 27, 1997 I wrote:
>
> Hi,
>
> while playing around with PL/Tcl I encountered a general
> memory allocation problem. Every transaction abort via
> elog(WARN, ...) leaves some allocated memory laying around.
>
> Just do some "select * from non_existing_table;" and you'll
> see the backend growing.
>
> One place where this happens is tcop. The querytree isn't
> freed on the restart. But there must be other places too
> since I've hacked out that one and the backend is still
> growing.
>
> This all didn't matter until we have triggers and constraints
> now. One normal action of a trigger or constraint is to fire
> a transaction abort. Thus, a really long running database
> backend can grow and grow.
>
> Please add this to TODO as I don't have the time right now to
> dive into.
Never got onto the TODO :-(
It still happens. Seems like approx 1K isn't freed per elog(ERROR).
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-25 19:02:19 | Re: [HACKERS] ecpg in docs |
Previous Message | Thomas G. Lockhart | 1998-02-25 17:36:26 | Re: [HACKERS] Platforms with v6.3 trouble |