Re: vacuum, performance, and MVCC - Mailing list pgsql-hackers

From Tom Lane
Subject Re: vacuum, performance, and MVCC
Date
Msg-id 6992.1151010374@sss.pgh.pa.us
Whole thread Raw
In response to Re: vacuum, performance, and MVCC  (Jim Nasby <jnasby@pervasive.com>)
List pgsql-hackers
Jim Nasby <jnasby@pervasive.com> writes:
> Question: do we currently create new index entries even if the index  
> key hasn't changed?

Yes.

> If so, what's the purpose of storing the CTID of  
> the next version in the old version of the row?

So that UPDATE can always find the newest version of the row,
independently of what indexes exist or how it got to the row.
You may care to re-read the second paragraph here:
http://developer.postgresql.org/docs/postgres/transaction-iso.html#XACT-READ-COMMITTED
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: Overhead for stats_command_string et al, take 2
Next
From: Tom Lane
Date:
Subject: Re: Overhead for stats_command_string et al, take 2