From: | "Anton Melser" <melser(dot)anton(at)gmail(dot)com> |
---|---|
To: | "David Lee Lambert" <as4109(at)wayne(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Questions about horizontal partitioning |
Date: | 2007-01-28 18:18:23 |
Message-ID: | 92d3a4950701281018i4c526b47v52a8ca611d3e3ae9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> However, if the primary key is entirely within those six columns, there
> will have to be an index on it in both tables to enforce the primary key
> constraint. In that case, an inner join could be performed with an index
> lookup or an index scan plus hash join, for a query that didn't use any
> other columns. Whether that translates into a significant I/O reduction
> depends on how wide and how frequently non-NULL those other columns are.
>
>
... if someone is feeling pedagogical (and the answer isn't that
complicated), could they explain why a simple index on the desired
columns wouldn't be the best solution?
Cheers
Antoine
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-28 18:20:16 | Re: Firing triggers based on certain Insert conditions |
Previous Message | Harpreet Dhaliwal | 2007-01-28 18:12:47 | Firing triggers based on certain Insert conditions |