Re: [BUGS] BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables

2010-07-27 Thread Robert Haas
On Tue, Jul 27, 2010 at 7:27 PM, Tom Lane wrote: > Robert Haas 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

Re: [BUGS] BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables

2010-07-27 Thread Tom Lane
Robert Haas 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 par

Re: [BUGS] BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables

2010-07-27 Thread Robert Haas
On Tue, Jul 6, 2010 at 2:20 PM, Ranga Gopalan wrote: > > The following bug has been logged online: > > Bug reference:      5543 > Logged by:          Ranga Gopalan > Email address:      ranga_gopa...@hotmail.com > PostgreSQL version: 8.4.4 > Operating system:   Linux x86-64 > Description:        P

[BUGS] BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables

2010-07-06 Thread Ranga Gopalan
The following bug has been logged online: Bug reference: 5543 Logged by: Ranga Gopalan Email address: ranga_gopa...@hotmail.com PostgreSQL version: 8.4.4 Operating system: Linux x86-64 Description:Poor performance - Index scan backwards not used for order by desc with