BRIN cost estimate - Mailing list pgsql-hackers

From Alvaro Herrera
Subject BRIN cost estimate
Date
Msg-id 20151116135239.GV614468@alvherre.pgsql
Whole thread Raw
Responses Re: BRIN cost estimate  (Emre Hasegeli <emre@hasegeli.com>)
List pgsql-hackers
Somebody wrote to me a few days ago that the BRIN cost estimation is
rather poor.  One immediately obvious issue which I think is easily
fixed is the correlation estimate, which is currently hardcoded to 1.

Since a BRIN scan always entails a scan of the relation in physical
order, it's simple to produce a better estimate for that, per the
attached patch.  (Note: trying to run this on expression indexes will
cause a crash.  I need to complete that part ...)

There are other improvements we've been discussing, but I'm unclear that
I will have time to study them to get a useful patch quickly enough.  If
somebody else wants to mess with this, please get in touch.

Thoughts?

--
Álvaro Herrera                            33.5S 70.5W

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Default Roles (was: Additional role attributes)
Next
From: Michael Paquier
Date:
Subject: Re: WIP: SCRAM authentication