Fixed sloppiness. Thanks to Kevin Grittner for catching this.

git-svn-id: file:///Users/dpage/pgweb/svn-repo/trunk@2834 8f5c7a92-453e-0410-a47f-ad33c8a6b003

diff --git a/portal/template/en/community/weeklynews/pwn20110410.html b/portal/template/en/community/weeklynews/pwn20110410.html
index 3e04846cf514ac786791dc9d19dbe39cc6bd70af..ae5aab99d72289db89e2fbfc047f2cf68e663d1a 100644 (file)
--- a/portal/template/en/community/weeklynews/pwn20110410.html
+++ b/portal/template/en/community/weeklynews/pwn20110410.html
@@ -124,6 +124,20 @@ Alvaro Herrera pushed:
 Robert Haas pushed:
 </p>
 
+<p>
+- Tweaks for SSI out-of-shared memory behavior.  If we call
+  hash_search() with HASH_ENTER, it will bail out rather than return
+  NULL, so it's redundant to check for NULL again in the caller.
+  Thus, in cases where we believe it's impossible for the hash table
+  to run out of slots anyway, we can simplify the code slightly.  On
+  the flip side, in cases where it's theoretically possible to run out
+  of space, we don't want to rely on dynahash.c to throw an error;
+  instead, we pass HASH_ENTER_NULL and throw the error ourselves if a
+  NULL comes back, so that we can provide a more descriptive error
+  message.  Kevin Grittner
+  <a href="http://git.postgresql.org/pg/commitdiff/56c7140ca813ba4c7ecb122a1d2b1268e705d092">http://git.postgresql.org/pg/commitdiff/56c7140ca813ba4c7ecb122a1d2b1268e705d092</a>
+</p>
+
 <p>
 - Include pid in pg_lock_status() results even for SIREAD locks.  Dan
   Ports.
@@ -174,11 +188,10 @@ Robert Haas pushed:
 
 <p>
 - Partially roll back overenthusiastic SSI optimization.  When a
-  regular lock is held, Steve Singer can use that in lieu of a
-  predicate lock to detect rw conflicts; but if the regular lock is
-  being taken by a subtransaction, we can't assume that it'll commit,
-  so releasing the parent transaction's lock in that case is a no-no.
-  Kevin Grittner
+  regular lock is held, SSI can use that in lieu of a predicate lock
+  to detect rw conflicts; but if the regular lock is being taken by a
+  subtransaction, we can't assume that it'll commit, so releasing the
+  parent transaction's lock in that case is a no-no.  Kevin Grittner
   <a href="http://git.postgresql.org/pg/commitdiff/fbc0d07796bcae8b2ee4b09ed236877338c95130">http://git.postgresql.org/pg/commitdiff/fbc0d07796bcae8b2ee4b09ed236877338c95130</a>
 </p>
 
@@ -343,20 +356,6 @@ Tom Lane pushed:
   <a href="http://git.postgresql.org/pg/commitdiff/73d9a908140e709b4cb12a8d2257a11baaec974f">http://git.postgresql.org/pg/commitdiff/73d9a908140e709b4cb12a8d2257a11baaec974f</a>
 </p>
 
-<p>
-- Tweaks for SSI out-of-shared memory behavior.  If we call
-  hash_search() with HASH_ENTER, it will bail out rather than return
-  NULL, so it's redundant to check for NULL again in the caller.
-  Thus, in cases where we believe it's impossible for the hash table
-  to run out of slots anyway, we can simplify the code slightly.  On
-  the flip side, in cases where it's theoretically possible to run out
-  of space, we don't want to rely on dynahash.c to throw an error;
-  instead, we pass HASH_ENTER_NULL and throw the error ourselves if a
-  NULL comes back, so that we can provide a more descriptive error
-  message.  Kevin Grittner
-  <a href="http://git.postgresql.org/pg/commitdiff/56c7140ca813ba4c7ecb122a1d2b1268e705d092">http://git.postgresql.org/pg/commitdiff/56c7140ca813ba4c7ecb122a1d2b1268e705d092</a>
-</p>
-
 <p>
 - Add an example of WITH (UPDATE RETURNING) INSERT to the INSERT ref
   page.  Per a discussion with Gavin Flower.  This barely scratches