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

From Gregory Stark
Subject Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1
Date
Msg-id 87zly1as4y.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1  (Mark Kirkwood <markir@paradise.net.nz>)
Responses Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1
List pgsql-performance
"Mark Kirkwood" <markir@paradise.net.nz> writes:

> Luke Lonergan wrote:
>> Sure - it's here:
>>   http://momjian.us/mhonarc/patches_hold/msg00381.html
>
> To clarify - we've fixed this in Greenplum db - the patch as submitted is
> (hopefully) a hint about how to fix it in Postgres, rather than a working
> patch... as its full of non-postgres functions and macros:

Oh, that was the problem with the original patch and I thought Luke had said
that was the problem which was fixed.

> 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...)

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's On-Demand Production Tuning

pgsql-performance by date:

Previous
From: ruben@rentalia.com
Date:
Subject: High Availability and Load Balancing
Next
From: Ketema
Date:
Subject: Improving Query