| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Amitabh Kant <amitabhkant(at)gmail(dot)com> |
| Cc: | Chetan Suttraway <chetan(dot)suttraway(at)enterprisedb(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Partitions and indexes |
| Date: | 2011-02-26 18:01:18 |
| Message-ID: | 4258A398-A6E4-441A-83BB-F69E46B6A26E@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 26 Feb 2011, at 18:04, Amitabh Kant wrote:
> Now if I partition the table T2 based on field T1id, making sure that each distinct T1id is provided its own child table
>
> Table T2C1 (inherited from T2, T1id field only contains 1 for all rows)
> Table T2C2 (inherited from T2, T1id field only contains 2 for all rows)
> --
> --
>
> What I would like to know here is that do I need to add an index for T1id field for either T2 or it's inherited tables (T2C1/T2C2 etc)?
No. Either would be rather pointless. In the child tables all the values in that index would have the same exact value, which you don't need as constraint exclusion already pointed the planner to the right table. In the parent table there wouldn't be any data to index.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4d69400211732483184779!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2011-02-26 18:22:38 | Re: Partitions and indexes |
| Previous Message | John R Pierce | 2011-02-26 17:46:39 | Re: Please help -- Postgres stopped responding .... |