On Thu, May 10, 2012 at 01:51:28PM -0400, Robert Haas wrote: > On Thu, May 10, 2012 at 1:44 PM, Bruce Momjian <br...@momjian.us> wrote: > > Not sure where to move that to. Source Code doesn't seem right. I > > moved it lower in the performance section. > > I'd just delete it. Instead, under index-only scans, I'd mention it > in the detail text: "This is possible because the visibility map has > been improved to be robust even in the face of database or system > crashes. Various race conditions that could result in incorrect data > in the visibility map have also been fixed."
OK, I merged it in in the attached, applied patch. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml new file mode 100644 index fc477c8..374ffb4 *** a/doc/src/sgml/release-9.2.sgml --- b/doc/src/sgml/release-9.2.sgml *************** *** 413,422 **** <para> This is often called "index-only scans" or "covering indexes". This is possible for heap pages with exclusively all-visible ! tuples, as reported by the visibility map. </para> </listitem> ! <listitem> <para> Allow frequently uncontended locks to be recorded using a new --- 413,423 ---- <para> This is often called "index-only scans" or "covering indexes". This is possible for heap pages with exclusively all-visible ! tuples, as reported by the visibility map. The visibility map was ! made crash-safe as a necessary part of implementing this feature. </para> </listitem> ! <listitem> <para> Allow frequently uncontended locks to be recorded using a new *************** *** 539,555 **** </para> </listitem> - <listitem> - <para> - Make the visibility map crash-safe (Robert Haas, Noah Misch) - </para> - - <para> - This helps vacuum be more efficient, and is necessary for - index-only scans. - </para> - </listitem> - <listitem> <para> Improve PowerPC and Itanium spinlock performance (Manabu Ori, --- 540,545 ----
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers