Re: Slow query performance on large table - Mailing list pgsql-performance

From Tomasz Myrta
Subject Re: Slow query performance on large table
Date
Msg-id 3E64E079.8050807@klaster.net
Whole thread Raw
In response to Slow query performance on large table  ("Paul McKay" <paul_mckay@clearwater-it.co.uk>)
Responses Re: Slow query performance on large table  (Andreas Pflug <Andreas.Pflug@web.de>)
Re: Slow query performance on large table  ("Paul McKay" <paul_mckay@clearwater-it.co.uk>)
List pgsql-performance
Andreas Pflug wrote:

> Tom,
>
> does this mean that a primary key alone might not be enough? As far as I
> understood Paul, the PK looks quite as the newly created index does, so
> "create index ind_meas on measurement (assessment,time)"  should perform
> the same as "... primary key(assessment,time)".
> Do possibly non-optimal indices (only assessment, only time as Paul
> described earlier) screw up the optimizer, igoring the better option
> usiing the PK? Obviously, the index used should be combined of
> (assessment,time) but IMHO a PK should be enough.
>
> regards,
>
> Andreas
You are right - primary key should be ok, but Paul lost it. psql \d
shows primary key indexes, but in this case there was no such primary key.

Regards,
Tomasz Myrta


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Slow query performance on large table
Next
From: Tomasz Myrta
Date:
Subject: Re: Slow query performance on large table