Re: Order by (for 15 rows) adds 30 seconds to query time - Mailing list pgsql-performance

From Tom Lane
Subject Re: Order by (for 15 rows) adds 30 seconds to query time
Date
Msg-id 21616.1259785526@sss.pgh.pa.us
Whole thread Raw
In response to Re: Order by (for 15 rows) adds 30 seconds to query time  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Order by (for 15 rows) adds 30 seconds to query time  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-performance
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Craig Ringer <craig@postnewspapers.com.au> wrote:
>> Doesn't the planner have some ... issues ... with estimation of
>> row counts on joins over unions? Or is my memory just more faulty
>> than usual?

> So far I can't tell if it's views with unions or (as I suspect)
> inheritance.

As of recent versions there shouldn't be a lot of difference between
inheritance and UNION ALL subqueries --- they're both "appendrels"
to the planner.  And yeah, I think the statistical support is pretty
crummy.

            regards, tom lane

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Order by (for 15 rows) adds 30 seconds to query time
Next
From: "Kevin Grittner"
Date:
Subject: Re: Order by (for 15 rows) adds 30 seconds to query time