This question pertains to PG 9.0.4 running on FreeBSD amd64. Was not
sure if it should go into the general list or the performance list, so
my apologies if I opted for the wrong list.
We currently have a db schema which contains many wide indices which
usually contain one column which is constan
Benjamin Krajmalnik wrote:
> From a performance standpoint, is there a big hit on select performance
> if a query ends up utilizing more than one index, taking into account
> that an index has been used already to reduce the data set of potential
> records, and the secondary index would mostly be
Thanks, Kevin.
That was my intent - if no column of an index changes in an update then no
changes are done on the index.
That helps quite a bit - I will try moving the columns which change
continuously to their own index - hopefully this will tame the overwhelming IO,
since the index will now ha
Benjamin Krajmalnik wrote:
> Kevin Grittner wrote:
>> Benjamin Krajmalnik wrote:
>>> I also assume that if no data has changed in an index, nothing
>>> is done when the record is updated as pertains to the
>>> particular index - am I correct in this assumption?
>>
>> No. [...] If any indexed colu
Thanks for the clarification. Now I understand - it is an all or nothing due
to required entries for each row version on the main table.
I will have to see if removing the constantly changing value from the indices
will affect the performance of our selects.
-Original Message-
From: Ke
