Re: ORDER BY and LIMIT not propagated on inherited - Mailing list pgsql-performance

From Matteo Beccati
Subject Re: ORDER BY and LIMIT not propagated on inherited
Date
Msg-id 43186922.4060703@beccati.com
Whole thread Raw
In response to Re: ORDER BY and LIMIT not propagated on inherited  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ORDER BY and LIMIT not propagated on inherited
List pgsql-performance
Hi,

>>The correct strategy IMHO would
>>be applying the order by and limit for each child table (which results
>>in an index scan, if possible), appending, then finally sorting a bunch
>>of rows, and limiting again.
>
> This would be a win in some cases, and in many others a loss (ie, wasted
> sort steps).  The hard part is determining when to apply it.

I don't actually know how many smaller separate sorts compare to a
single big sort, but I guess the difference wouldn't be so big if the
LIMIT is low. Add to this that you don't need to append the whole
rowsets, but just smaller ones.


Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: ORDER BY and LIMIT not propagated on inherited
Next
From: Jens-Wolfhard Schicke
Date:
Subject: Re: ORDER BY and LIMIT not propagated on inherited