Re: Choice of bitmap scan over index scan

From: Jeremy Harris <jgh(at)wizmail(dot)org>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Choice of bitmap scan over index scan
Date: 2010-01-11 19:41:08
Message-ID: 4B4B7ED4.8070208@wizmail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 01/11/2010 02:53 AM, Robert Haas wrote:
> On Sun, Jan 10, 2010 at 9:04 AM, Jeremy Harris<jgh(at)wizmail(dot)org> wrote:
>> Needing to use an external (on-disk) sort method, when taking
>> only 90MB, looks odd.
[...]
> Well, you'd need to have work_mem> 90 MB for that not to happen, and
> very few people can afford to set that setting that high. If you have
> a query with three or four sorts using 90 MB a piece, and five or ten
> users running them, you can quickly kill the box...

Oh. That's, um, a real pity given the cost of going external. Any hope
of a more dynamic allocation of memory resource in the future?
Within a single query plan, the number of sorts is known; how about
a sort-mem limit per query rather than per sort (as a first step)?

Cheers,
Jeremy

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2010-01-11 19:45:44 Re: performance config help
Previous Message Scott Marlowe 2010-01-11 19:38:42 Re: performance config help