"Tom Lane" <[EMAIL PROTECTED]> writes: > The only case where the optimization is a win is where you have a > zero-startup-cost subplan, and the only way to get sorted output with zero > startup cost is an indexscan.
Sure but there could be other nodes above the index scan which preserve the order. In particular nested loop and merge joins. Unique also preserves the order but I can't see how it could be useful here. And of course potentially Append nodes in the future... -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
