Re: BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables
Date
Msg-id 18032.1280273262@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> Does it help if you put a CHECK (false) constraint on the parent table?

It won't --- it'll still result in an append plan even if there's only
one surviving child.

This is one of many things that seem to me to not make sense to tackle
until we have an explicit notion of partitioning.  Having the planner
try to prove from individual constraints that it could get a correctly
sorted Append result without an explicit sort step would be hugely
expensive, and complicated --- imagine even trying to pick out the
relevant indexes without any infrastructure to help identify them.
With a partitioned structure we could understand that a-priori.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables
Next
From: Robert Haas
Date:
Subject: Re: BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables