Skip site navigation (1) Skip section navigation (2)

pgsql-server: Revise ResourceOwner code to avoid accumulating

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server: Revise ResourceOwner code to avoid accumulating
Date: 2004-08-25 18:43:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Revise ResourceOwner code to avoid accumulating ResourceOwner objects
for every command executed within a transaction.  For long transactions
this was a significant memory leak.  Instead, we can delete a portal's
or subtransaction's ResourceOwner immediately, if we physically transfer
the information about its locks up to the parent owner.  This does not
fully solve the leak problem; we need to do something about counting
multiple acquisitions of the same lock in order to fix it.  But it's a
necessary step along the way.

Modified Files:
        xact.c (r1.178 -> r1.179)
        portalmem.c (r1.68 -> r1.69)
        README (r1.2 -> r1.3)
        resowner.c (r1.2 -> r1.3)

pgsql-committers by date

Next:From: Tom LaneDate: 2004-08-25 20:07:57
Subject: pgsql-server: Fix typo in comment, per Andrew Dunstan.
Previous:From: Dennis BjorklundDate: 2004-08-25 18:36:56
Subject: Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group