Tim Uckun wrote:
> I dropped the index and the numbers shot up tenfold or more. I don't
> know why postgres feels the need to update the GIN index on the hstore
> field when I am only updating an integer field but it looks like I
> need to split the hstore into a different table.
Every UPDATE that is not HOT will create a row version with
a new "row id". That means that all indexes referencing that
row will have to get updated.
That is consistent with better performance with low fillfactor
(which makes HOT more likely).
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
