From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Sriram Dandapani <sdandapani(at)counterpane(dot)com> |
Cc: | "Pgsql-Performance (E-mail)" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: select max(column) from parent table very slow |
Date: | 2006-08-25 01:08:49 |
Message-ID: | 44EE4DA1.5060701@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Sriram Dandapani wrote:
> Parent table has a column say column1 which is indexed (parent table and
> all child tables are indexed on that column)
>
Do you mean?
select max(foo) from bar;
In older versions of postgresql that would scan the whole table. In 8.1
and above it doesn't. However, I am guess that since this is a
partitioned table the planner isn't smart enough to just perform the
query on each child and a max on the set that is returned. Thus you are
scanning each table completely.
But that is just a guess.
Joshua D. Drake
>
>
> When a select max(column1) is done on parent table..takes a very long
> time to get back with the result
>
> The same query on a child table gives instantaneous response (the tables
> are quite large appx.each child table has about 20-30 million rows)
>
>
>
> Constraint exclusion is turned on. The column is not the basis for
> partitioning. Postgres 8.1.2
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-08-25 04:33:27 | Re: select max(column) from parent table very slow |
Previous Message | Sriram Dandapani | 2006-08-24 23:43:53 | select max(column) from parent table very slow |