Re: Sort memory not being released - Mailing list pgsql-general

From Tom Lane
Subject Re: Sort memory not being released
Date
Msg-id 12671.1055861139@sss.pgh.pa.us
Whole thread Raw
In response to Re: Sort memory not being released  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Sort memory not being released
Re: Sort memory not being released
List pgsql-general
Martijn van Oosterhout <kleptog@svana.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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Damn triggers and NEW
Next
From: Stephan Szabo
Date:
Subject: Re: adddepend and partial indexes