Row versions and indexes - Mailing list pgsql-general

From Jack Orenstein
Subject Row versions and indexes
Date
Msg-id 7ecd811f0609281458q794cb1c1ybcfdd38ad1039250@mail.gmail.com
Whole thread Raw
Responses Re: Row versions and indexes  (Alan Hodgson <ahodgson@simkin.ca>)
Re: Row versions and indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Suppose I have a table and index:

    create table t(x int, y varchar, primary key(x));

and that the only updates are "update t set y = ... where x = ?".

I understand that updating a row of t generates a new row version, and
that different transactions may see different versions of the same
row.

How does versioning work for the index?

- The update above does not update the index key. Does the index get
  updated at all?

- If not, then how can an index lookup return the correct version of
  selected rows?

This aspect of versioning has never been clear to me. Now there's a cost
issue involved, as I need to update every row in a large table, never
updating the index key. Will this run faster if I drop the index?
(Yes, I can run the experiment, but I'd like to understand the
fundamentals better.)

Jack Orenstein

pgsql-general by date:

Previous
From: Ben
Date:
Subject: Re: contrib/levenshtein() has a bug?
Next
From: Alan Hodgson
Date:
Subject: Re: Row versions and indexes