Re: Fwd: Statistics and selectivity estimation for ranges

Lists: pgsql-hackers
From: Matthias <nitrogenycs(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Statistics and selectivity estimation for ranges
Date: 2012-08-06 16:00:59
Message-ID: CACECd8jT=t=KVRpdkPYxYN-5ny5wneiAnGj0igo+h8vm0QwXwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Having statistics on ranges was really missing! The planner was doing
some really, really bad choices on bigger tables regarding seq/random
scans, nested loop/other joins etc.

Is there any chance this makes it into 9.2 final? It would really
round-off the introduction of range types and maybe avoid problems
like "the new range types are slow" (just due to the bad row
estimates).

Thanks for implementing this feature,
-Matthias


From: Matthias <nitrogenycs(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Fwd: Statistics and selectivity estimation for ranges
Date: 2012-08-06 16:08:41
Message-ID: CACECd8jrJ69vfPh-s0D3ywDyrw4_qNSJ9GEC3B81m2BGW7GQXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Having statistics on ranges was really missing! The planner was doing
some really, really bad choices on bigger tables regarding seq/random
scans, nested loop/other joins etc.

Is there any chance this makes it into 9.2 final? It would really
round-off the introduction of range types and maybe avoid problems
like "the new range types are slow" (just due to the bad row
estimates).

Thanks for implementing this feature,
-Matthias


From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fwd: Statistics and selectivity estimation for ranges
Date: 2012-08-06 17:19:28
Message-ID: 501FFCA0.2070201@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


> Is there any chance this makes it into 9.2 final? It would really
> round-off the introduction of range types and maybe avoid problems
> like "the new range types are slow" (just due to the bad row
> estimates).

Nope, that's strictly a 9.3 feature. 9.2 is in beta2.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com