From: | momjian(at)postgresql(dot)org (Bruce Momjian) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Update entry: < * Allow heap reuse of UPDATEd rows if old and |
Date: | 2006-06-24 23:47:58 |
Message-ID: | 20060624234758.30B989FA5DD@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Update entry:
< * Allow heap reuse of UPDATEd rows if old and new versions are on the
< same heap page?
> * Allow heap reuse of UPDATEd rows if no indexed columns are changed,
> and old and new versions are on the same heap page?
< This is possible for same-page updates because a single index row
< can point to both old and new values.
> While vacuum handles DELETEs fine, updating of non-indexed columns, like
> counters, are difficult for VACUUM to handle efficiently. This method
> is possible for same-page updates because a single index row can be
> used to point to both old and new values.
Modified Files:
--------------
pgsql/doc:
TODO (r1.1897 -> r1.1898)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1897&r2=1.1898)
pgsql/doc/src/FAQ:
TODO.html (r1.400 -> r1.401)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.400&r2=1.401)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-06-25 00:18:25 | pgsql: Fix Win32/Cygwin problems: After updating to the latest cvs, and |
Previous Message | Bruce Momjian | 2006-06-24 23:45:02 | pgsql: Add UPDATE entry for row reuse. |