Re: Releasing memory during External sorting?

From: Pailloncy Jean-Gerard <jg(at)rilk(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Releasing memory during External sorting?
Date: 2005-09-23 16:39:35
Message-ID: AC85B14C-FFB0-455B-88E3-6997B46269BE@rilk.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

> On most platforms it's quite unlikely that any memory would
> actually get
> released back to the OS before transaction end, because the memory
> blocks belonging to the tuplesort context will be intermixed with
> blocks
> belonging to other contexts. So I think this is pretty pointless.
> (If you can't afford to have the sort using all of sort_mem, you've
> set
> sort_mem too large, anyway.)
On OpenBSD 3.8 malloc use mmap(2) and no more sbrk.
So, as soon as the bloc is free, it returns to the OS.
Access to the freed pointer crashs immediatly.

Cordialement,
Jean-Gérard Pailloncy

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lee, Patricia S. 2005-09-23 16:45:55 PgAdmin3 1.2.2 Install on Win32 Disrupts Pg Service
Previous Message Bricklen Anderson 2005-09-23 16:35:14 Re: R: Table Partitioning is in 8.1

Browse pgsql-performance by date

  From Date Subject
Next Message Ahmad Fajar 2005-09-23 16:40:05 Re: tsearch2 seem very slow
Previous Message Stef 2005-09-23 16:16:44 Re: VACUUM FULL vs CLUSTER