| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Johansen <davejohansen(at)gmail(dot)com> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: MAX() and multi-column index on a partitioned table? |
| Date: | 2015-05-23 01:13:50 |
| Message-ID: | 21054.1432343630@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Dave Johansen <davejohansen(at)gmail(dot)com> writes:
> On Fri, May 22, 2015 at 3:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What PG version are you using? 9.1 or newer should know how to do this
>> with a merge append of several indexscans.
> Sorry, I should have mentioned that in the original email. I'm using 8.4.20
> on RHEL 6. From your reply, it sounds like this is the expected behavior
> for 8.4 and 9.0. Is that the case?
Yeah, pre-9.1 is not very bright about that. You could factor the query
manually, perhaps, though it's surely a pain in the neck.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tory M Blue | 2015-05-27 07:50:51 | ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 |
| Previous Message | Dave Johansen | 2015-05-22 23:53:19 | Re: MAX() and multi-column index on a partitioned table? |