From fc6a2293b59e2c2e9d76bbc20df9bd194a9b00cd Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 24 Jun 2006 23:45:02 +0000 Subject: Add UPDATE entry for row reuse. > > * Allow heap reuse of UPDATEd rows if 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. > http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php --- doc/TODO | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'doc/TODO') diff --git a/doc/TODO b/doc/TODO index 7200d10736f..826ef81869d 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sun Jun 18 15:32:30 EDT 2006 +Last updated: Sat Jun 24 19:44:48 EDT 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1131,6 +1131,13 @@ Vacuum http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php +* Allow heap reuse of UPDATEd rows if 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. + http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php + * Auto-vacuum o Use free-space map information to guide rfilling -- cgit v1.2.3