| From: | "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com> |
|---|---|
| To: | Anj Adu <fotographs(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: select max(parent_table) slow |
| Date: | 2009-08-18 13:38:28 |
| Message-ID: | BD69807DAE0CE44CA00A8338D0FDD08340FBDCBF@oma00cexmbx03.corp.westworlds.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
What is your constraint_exclusion config set to on your new instance?
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Anj Adu
Sent: Tuesday, August 18, 2009 8:30 AM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] select max(parent_table) slow
We are testing 8.4 and noticed that the performance of
select max(indexed_col) from parent_Table
is the same (slow) as postgres 8.1.x ( our current version). The
child tables are huge and the indexed_col is not the basis for
partitioning.
I remember that this was an issue from an earlier thread where the
optimizer was not able to use the child partitions only to get the max
value. Is this true for 8.4 ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2009-08-18 13:42:32 | Re: select max(parent_table) slow |
| Previous Message | Kenneth Marshall | 2009-08-18 13:38:09 | Re: select max(parent_table) slow |