Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1 - Mailing list pgsql-performance

From Mark Kirkwood
Subject Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1
Date
Msg-id 472EAEE6.2090000@paradise.net.nz
Whole thread Raw
In response to Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-performance
Gregory Stark wrote:
> cdbpathlocus_pull_above_projection
>
>
> In particular this is the function I was hoping to see. Anyways as Tom pointed
> out previously there's precedent in Postgres as well for subqueries so I'm
> sure I'll be able to do it.
>
> (But I'm still not entirely convinced putting the append member vars into the
> eclasses would be wrong btw...)
>
>
I spent today looking at getting this patch into a self contained state.
Working against HEAD I'm getting bogged down in the PathKeyItem to
PathKey/EquivalenceClass/EquivalenceMember(s) change. So I figured I'd
divide and conquer to some extent, and initially provide a patch:

- against 8.2.(5)
- self contained  (i.e no mystery functions)

The next step would be to update to to HEAD. That would hopefully
provide some useful material for others working on this.

Thoughts suggestions?

regards

Mark


pgsql-performance by date:

Previous
From: Greg Smith
Date:
Subject: Re: Migrating to 8.3 - checkpoints and background writer
Next
From: Gregory Stark
Date:
Subject: Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1