From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Craig Boucher <craig(at)wesvic(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Column order in multi column primary key |
Date: | 2016-08-08 20:41:39 |
Message-ID: | CAKFQuwa0Bso+3tDXJiHwBzNqg9PsFu0yD0yM=FW84z1=4Gab9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 8, 2016 at 4:35 PM, Craig Boucher <craig(at)wesvic(dot)com> wrote:
> Thanks David. I’ve thought about the hierarchy you mentioned but the
> hierarchy can change and I need to capture it as it was when the data was
> generated.
>
>
>
> I should have pointed out in my last response that I was wondering if the
> performance of the pk index on work_session would be better if my primary
> key was (customer_id, work_session_id) or if (work_session_id,
> customer_id) will be fine. Customer_id will be repeated quite a bit in
> the table but work_session_id should be unique across the whole table.
>
>
>
I answered that in the original response...for PKs to operate most
efficiently the most selective attribute should come first.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-08-08 20:46:38 | Re: Column order in multi column primary key |
Previous Message | Craig Boucher | 2016-08-08 20:35:02 | Re: Column order in multi column primary key |