Re: Partitions and indexes - Mailing list pgsql-general

From John R Pierce
Subject Re: Partitions and indexes
Date
Msg-id 4D6944EE.6070208@hogranch.com
Whole thread Raw
In response to Re: Partitions and indexes  (Alban Hertroys <dalroi@solfertje.student.utwente.nl>)
Responses Re: Partitions and indexes  (Amitabh Kant <amitabhkant@gmail.com>)
List pgsql-general
On 02/26/11 10:01 AM, Alban Hertroys wrote:
> 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
therewouldn't be any data to index. 

the whole idea of one table per row sounds rather odd and pointless to me.

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: Partitions and indexes
Next
From: Amitabh Kant
Date:
Subject: Re: Partitions and indexes