Re: Sort memory not being released

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Sean Chittenden <sean(at)chittenden(dot)org>, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Sort memory not being released
Date: 2003-06-17 14:45:39
Message-ID: 12671.1055861139@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> For large allocations glibc tends to mmap() which does get unmapped. There's
> a threshold of 4KB I think. Ofcourse, thousands of allocations for a few
> bytes will never trigger it.

But essentially all our allocation traffic goes through palloc, which
bunches small allocations together. In typical scenarios malloc will
only see requests of 8K or more, so we should be in good shape on this
front.

(Not that this is very relevant to Jim's problem, since he's not using
glibc...)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sven Köhler 2003-06-17 14:46:27 Re: full featured alter table?
Previous Message Bruno Wolff III 2003-06-17 14:44:03 Re: postgreSQL on NAS/SAN?