postgresql/src/backend/access
Tom Lane fe455ee1d4 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.
2004-08-25 18:43:43 +00:00
..
common Infrastructure for I/O of composite types: arrange for the I/O routines 2004-06-06 00:41:28 +00:00
gist Invent ResourceOwner mechanism as per my recent proposal, and use it to 2004-07-17 03:32:14 +00:00
hash Invent ResourceOwner mechanism as per my recent proposal, and use it to 2004-07-17 03:32:14 +00:00
heap Invent WAL timelines, as per recent discussion, to make point-in-time 2004-07-21 22:31:26 +00:00
index Tweak indexscan and seqscan code to arrange that steps from one page to 2004-04-21 18:24:26 +00:00
nbtree Fix bug introduced into _bt_getstackbuf() on 2003-Feb-21: the initial 2004-08-17 23:15:33 +00:00
rtree Invent ResourceOwner mechanism as per my recent proposal, and use it to 2004-07-17 03:32:14 +00:00
transam Revise ResourceOwner code to avoid accumulating ResourceOwner objects 2004-08-25 18:43:43 +00:00
Makefile $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00