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

Re: memory leaks? using savepoint

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuhito Kasahara <kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: memory leaks? using savepoint
Date: 2010-12-16 22:27:22
Message-ID: 15534.1292538442@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Tatsuhito Kasahara <kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp> writes:
> When I tested simple query as following, backend process used much memory
> and not freed until the backend was finished.
> # This is reproduced on PostgreSQL8.3 (PostgreSQL8.3.6 - PostgreSQL8.3.12)

Hmm ... this test case doesn't appear to produce any significant memory
leakage in 8.4 and up.  What is happening in 8.3 is that the
CurTransactionContext of each subtransaction becomes nonempty, so it
eats 8K or so even though the snapshot gets released shortly later.
There are plenty of other ways to cause that to happen, though, so I'm
not particularly excited about fixing this one ... especially not in a
stable branch that's not getting a lot of developer testing anymore.
I'm inclined to leave this alone --- I think the risks of patching only
an old branch will outweigh the benefits.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: E.B BenoygopalDate: 2010-12-17 04:03:50
Subject: BUG #5791: Tables are not viewing through pgadmin
Previous:From: Tom LaneDate: 2010-12-16 17:56:12
Subject: Re: [Fwd: DBD::Pg on HP-UX 11.31 64bit]

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