Re: Idea how to get rid of Bitmap Heap Scan

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: "Michael N(dot) Mikhulya" <m(dot)mikhulya(at)gmail(dot)com>, Matthew Wakeling <matthew(at)flymine(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Idea how to get rid of Bitmap Heap Scan
Date: 2009-12-20 02:11:55
Message-ID: 603c8f070912191811p75306db3jd82c5f1b891a4a64@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Dec 18, 2009 at 12:29 PM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> A word of warning, in my experience the hardest part for changes like
> this isn't the executor changes (which in this case wouldn't be far
> from easy) but the planner changes to detect when this new plan would
> be better.

There's also the problem of making the visibility map crash-safe. I
think I heard you might have some ideas on that one - has it been
discussed on -hackers?

...Robert

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Stark 2009-12-20 11:37:45 Re: Idea how to get rid of Bitmap Heap Scan
Previous Message Robert Haas 2009-12-19 03:33:26 Re: Automatic optimization of IN clauses via INNER JOIN