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

Re: BUG #6365: Memory leak in insert and update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: havasvolgyi(dot)otto(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6365: Memory leak in insert and update
Date: 2011-12-29 22:42:04
Message-ID: 29928.1325198524@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Thu, Dec 29, 2011 at 2:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I see no memory leak with this example.

> This is by the way a FAQ:
> http://wiki.postgresql.org/wiki/FAQ#Why_does_PostgreSQL_use_so_much_memory.3F

Well, to be fair, the FAQ entry didn't mention this behavior of reported
usage increasing over time.  But it seems like a good place to document
that, so I just added a paragraph about it.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Gavin FlowerDate: 2011-12-29 23:51:56
Subject: Re: converting between infinity timestamp and float8 (epoch)
Previous:From: Merlin MoncureDate: 2011-12-29 21:57:51
Subject: Re: with hold cursor, cause function execute twice and wrong result

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