From: | Shelby Cain <alyandon(at)yahoo(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: possible memory leak in 8.0 beta 1 |
Date: | 2004-09-01 17:29:16 |
Message-ID: | 20040901172916.81411.qmail@web41601.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- Shelby Cain <alyandon(at)yahoo(dot)com> wrote:
[stuff about memory leaking snipped]
I see the following in the beta 2 changelog:
2004-08-25 15:43 tgl
* src/backend/: access/transam/xact.c,
utils/mmgr/portalmem.c, utils/resowner/README,
utils/resowner/resowner.c: 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.
Is this what I'm seeing?
Regards,
Shelby Cain
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-09-01 17:33:28 | Re: possible memory leak in 8.0 beta 1 |
Previous Message | Shelby Cain | 2004-09-01 17:21:06 | possible memory leak in 8.0 beta 1 |