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

From Zeugswetter Andreas DCP SD
Subject Re: vacuum, performance, and MVCC
Date
Msg-id E1539E0ED7043848906A8FF995BDA579011EFDA7@m0143.s-mxs.net
Whole thread Raw
In response to vacuum, performance, and MVCC  ("Mark Woodward" <pgsql@mohawksoft.com>)
List pgsql-hackers
> >> Each time the record is updated, a new version is created, thus
> >> lengthening the "correct" version search each time row is accessed,

> >> until, of course, the next vacuum comes along and corrects the
index
> >> to point to the latest version of the record.
> >>
> >> Is that a fair explanation?
> >
> > No, it's not.
> >
> > 1.  The index points to all the versions, until they get vacuumed
out.

> it points to the last "current" version as updated by vacuum, or the
first version
> of the row.

no, the index has one entry for each version of the row.
This is why updating only non-indexed columns is relatively expensive
in pg.

Andreas


pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: Re: vacuum, performance, and MVCC
Next
From: "Diogo Biazus"
Date:
Subject: xlog viewer proposal