From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, Michael Fuhr <mike(at)fuhr(dot)org>, Lonni J Friedman <netllama(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: changing sort_mem on the fly? |
Date: | 2005-01-30 18:05:15 |
Message-ID: | 3774.1107108315@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Jim C. Nasby" <decibel(at)decibel(dot)org> writes:
> On Sun, Jan 30, 2005 at 08:50:49PM +1100, Neil Conway wrote:
>> Do you have any thoughts on how to improve it?
> See http://archives.postgresql.org/pgsql-general/2003-06/msg01072.php
> and http://archives.postgresql.org/pgsql-general/2003-06/msg01089.php
All of this falls down on twin problems: (1) we have no portable way to
find out how much RAM is really available, and (2) the planner has to
make a cost estimate for the sort in advance of actual runtime --- which
requires making some assumption about the value of sort_mem that will be
used.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-30 19:04:16 | Re: Freeradius and Postgresql |
Previous Message | Tom Lane | 2005-01-30 17:55:28 | Re: [GENERAL] MySQL worm attacks Windows servers |