From: David Fetter <david@fetter.org>
Date: Mon, 9 May 2011 05:16:06 +0000 (+0000)
Subject: PostgreSQL Weekly News May 08, 2011
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=8afcc2b78ef893fda7045874a94a88e38415611f;p=pgweb-old.git

PostgreSQL Weekly News May 08, 2011

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

diff --git a/portal/files/weeklynews.xml b/portal/files/weeklynews.xml
index 4fe0f0b1..ce431ab4 100644
--- a/portal/files/weeklynews.xml
+++ b/portal/files/weeklynews.xml
@@ -10,6 +10,17 @@
 <description></description>
 <language>en</language>
 
+<item>
+<title>PostgreSQL Weekly News May 8th 2011</title>
+<description>
+PostgreSQL 9.1 beta 1 is out.  Test!
+&#x3C;a href=&#x22;http://www.postgresql.org/developer/beta&#x22;&#x3E;http://www.postgresql.org/developer/beta&#x3C;/a&#x3E;
+
+
+</description>
+<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110508</guid>
+<pubDate>Sun, 08 May 2011 00:00:00 PST</pubDate>
+</item>
 <item>
 <title>PostgreSQL Weekly News May 1st 2011</title>
 <description>
@@ -115,16 +126,5 @@ This is the last planned alpha for 9.1.  You can get it here:
 <guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110313</guid>
 <pubDate>Sun, 13 Mar 2011 00:00:00 PST</pubDate>
 </item>
-<item>
-<title>PostgreSQL Weekly News March 6th 2011</title>
-<description>
-The list of talks and speakers for PGCon 2011 has been released.
-&#x3C;a href=&#x22;http://www.pgcon.org/2011/schedule/day_2011-05-19.en.html&#x22;&#x3E;http://www.pgcon.org/2011/schedule/day_2011-05-19.en.html&#x3C;/a&#x3E;
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110306</guid>
-<pubDate>Sun, 06 Mar 2011 00:00:00 PST</pubDate>
-</item>
 </channel>
 </rss>
\ No newline at end of file
diff --git a/portal/template/en/community/weeklynews.html b/portal/template/en/community/weeklynews.html
index 19b99ad1..942cd365 100644
--- a/portal/template/en/community/weeklynews.html
+++ b/portal/template/en/community/weeklynews.html
@@ -11,6 +11,7 @@ Weekly News
 <p>Here is the <a href="http://www.postgresql.org/files/weeklynews.xml">RSS feed</a>.</p>
 
 <ul>
+    <li><a href="/community/weeklynews/pwn20110508">May 8th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110501">May 1st 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110424">April 24th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110417">April 17th 2011</a></li>
diff --git a/portal/template/en/community/weeklynews/pwn20110501.html b/portal/template/en/community/weeklynews/pwn20110501.html
index bb4bb2df..a251aa59 100644
--- a/portal/template/en/community/weeklynews/pwn20110501.html
+++ b/portal/template/en/community/weeklynews/pwn20110501.html
@@ -315,7 +315,7 @@ Tom Lane pushed:
 <p>
 - Fix pg_size_pretty() to avoid overflow for inputs close to
   INT64_MAX.  The expression that tried to round the value to the
-  nearest Tim Bunce could overflow, leading to bogus output as
+  nearest TB could overflow, leading to bogus output as
   reported in bug #5993 from Nicola Cossu.  This isn't likely to ever
   happen in the intended usage of the function (if it could, we'd be
   needing to use a wider datatype instead); but it's not hard to give
diff --git a/portal/template/en/community/weeklynews/pwn20110508.html b/portal/template/en/community/weeklynews/pwn20110508.html
new file mode 100644
index 00000000..5926d0de
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110508.html
@@ -0,0 +1,427 @@
+<!-- BEGIN page_title_block -->
+Weekly News - May 08 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - May 08 2011</h1>
+
+<p>
+PostgreSQL 9.1 beta 1 is out.  Test!
+<a href="http://www.postgresql.org/developer/beta">http://www.postgresql.org/developer/beta</a>
+</p>
+
+<p>
+AustinPUG will meet on May 11 at 7 p.m in Austin, Texas, USA.  Free
+Pizza!  To get fed, RSVP to <austinpug AT postgresql DOT org>.
+<a href="http://pugs.postgresql.org/austinpug">http://pugs.postgresql.org/austinpug</a>
+</p>
+
+<p>
+CHAR(11), the PostgreSQL Conference on Clustering, High Availability
+and Replication is now open for online registration and bookings.
+July 11-12 2011 in Cambridge, UK.
+<a href="http://www.char11.org/">http://www.char11.org/</a>
+</p>
+
+<p>
+PostgreSQL Confernece West (#PgWest) will be held September 27th-30th,
+2011 at the San Jose Convention center in San Jose, California, USA.
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+pgbuildfarm client 4.5 released.
+<a href="http://pgfoundry.org/forum/forum.php?forum_id=1833">http://pgfoundry.org/forum/forum.php?forum_id=1833</a>
+</p>
+
+<p>
+pgpool-II 3.1.0 alpha2, a connection pooler and more, released.
+<a href="http://pgfoundry.org/projects/pgpool/">http://pgfoundry.org/projects/pgpool/</a>
+</p>
+
+<h2>PostgreSQL Jobs for May</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-05/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-05/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+PGCon will be May 19-20, 2011 at the University of Ottawa, preceded by
+two days of tutorials on May 17-18.
+<a href="http://www.pgcon.org/2011/">http://www.pgcon.org/2011/</a>
+</p>
+
+<p>
+PG Session 2, on PostGIS, will be held on June 23rd in Paris.  The CfP
+is open!
+<a href="http://www.postgresql-sessions.org/en/2/">http://www.postgresql-sessions.org/en/2/</a>
+</p>
+
+<p>
+PostgreSQL Conference Europe 2011 will be held on October 18-21 in
+Amsterdam.
+<a href="http://2011.pgconf.eu/">http://2011.pgconf.eu/</a>
+</p>
+
+<p>
+pgbr will be in Sao Paulo, Brazil November 3-4, 2011.
+<a href="http://pgbr.postgresql.org.br/">http://pgbr.postgresql.org.br/</a>
+</p>
+
+<h2>PostgreSQL in the News</h2>
+<p>
+Planet PostgreSQL: <a href="http://planet.postgresql.org/">http://planet.postgresql.org/</a>
+</p>
+
+<p>
+PostgreSQL Weekly News is brought to you this week by David Fetter
+</p>
+
+<p>
+Submit news and announcements by Sunday at 3:00pm Pacific time.
+Please send English language ones to david@fetter.org, German language
+to pwn@pgug.de, Italian language to pwn@itpug.org.  Spanish language
+to pwn@arpug.com.ar.
+</p>
+
+<h2>Reviews</h2>
+<h2>Applied Patches</h2>
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Improve aset.c's space management in contexts with small
+  maxBlockSize.  The previous coding would allow requests up to half
+  of maxBlockSize to be treated as "chunks", but when that actually
+  did happen, we'd waste nearly half of the space in the malloc block
+  containing the chunk, if no smaller requests came along to fill it.
+  Avoid this scenario by limiting the maximum size of a chunk to 1/8th
+  maxBlockSize, so that we can waste no more than 1/8th of the
+  allocated space.  This will not change the behavior at all for the
+  default context size parameters (with large maxBlockSize), but it
+  will change the behavior when using ALLOCSET_SMALL_MAXSIZE.  In
+  particular, there's no longer a need for spell.c to be overly
+  concerned about the request size parameters it uses, so remove a
+  rather unhelpful comment about that.  Merlin Moncure, per an idea of
+  Tom Lane's
+  <a href="http://git.postgresql.org/pg/commitdiff/6755558b92748287e961fed518c14be375630464">http://git.postgresql.org/pg/commitdiff/6755558b92748287e961fed518c14be375630464</a>
+</p>
+
+<p>
+- Fix pull_up_sublinks' failure to handle nested pull-up
+  opportunities.  After finding an EXISTS or ANY sub-select that can
+  be converted to a semi-join or anti-join, we should recurse into the
+  body of the sub-select.  This allows cases such as
+  EXISTS-within-EXISTS to be optimized properly.  The original coding
+  would leave the lower sub-select as a SubLink, which is no better
+  and often worse than what we can do with a join.  Per example from
+  Wayne Conrad.  Back-patch to 8.4.  There is a related issue in older
+  versions' handling of pull_up_IN_clauses, but they're lame enough
+  anyway about the whole area that it seems not worth the extra work
+  to try to fix.
+  <a href="http://git.postgresql.org/pg/commitdiff/dcc685debb02c507b88aa8052f9e6334a7c3f830">http://git.postgresql.org/pg/commitdiff/dcc685debb02c507b88aa8052f9e6334a7c3f830</a>
+</p>
+
+<p>
+- Include unary plus in the Operator Precedence table.  Per gripe from
+  Grzegorz Szpetkowski.  Also, change the subsection heading from
+  "Lexical Precedence" (which is a contradiction in terms) to
+  "Operator Precedence".
+  <a href="http://git.postgresql.org/pg/commitdiff/671322751add80f3368cd9ef17134fb9f73cf747">http://git.postgresql.org/pg/commitdiff/671322751add80f3368cd9ef17134fb9f73cf747</a>
+</p>
+
+<p>
+- Remove precedence labeling of keywords TRUE, FALSE, UNKNOWN, and
+  ZONE.  These were labeled with precedences just to avoid attaching
+  explicit precedences to the productions in which they were the last
+  terminal symbol.  Since a terminal symbol precedence marking can
+  affect many other things too, it seems like better practice to
+  attach precedence labels to the productions, and not mark the
+  terminal symbols.  Ideally we'd also remove the precedence attached
+  to NULL_P, but it turns out that we are actually depending on that
+  having a precedence higher than POSTFIXOP, else we get a
+  shift/reduce conflict for postfix operators in b_expr.  (Which more
+  or less proves my point about these markings having a high risk of
+  unexpected consequences.)  For the moment, move NULL_P into the set
+  of keywords grouped with IDENT, so that at least it will act
+  similarly to non-keywords; and document the interaction.
+  <a href="http://git.postgresql.org/pg/commitdiff/12b7164578e73abb065a835c588c1e0c44670ed3">http://git.postgresql.org/pg/commitdiff/12b7164578e73abb065a835c588c1e0c44670ed3</a>
+</p>
+
+<p>
+- Move RegisterPredicateLockingXid() call to a safer place.  The SSI
+  patch inserted a call of RegisterPredicateLockingXid into
+  GetNewTransactionId, which was a bad idea on a couple of grounds.
+  First, it's not necessary to hold XidGenLock while manipulating that
+  shared memory, and doing so is bad because XidGenLock is a
+  high-contention lock that should be held for as short a time as
+  possible.  (Not to mention that it adds an entirely unnecessary
+  deadlock hazard, since we must take SerializableXactHashLock as
+  well.)  Second, the specific place where it was put was between
+  extending CLOG and advancing nextXid, which could result in
+  unpleasant behavior in case of a failure there.  Pull the call out
+  to AssignTransactionId, which is much safer and arguably better from
+  a modularity standpoint too.  There is more work to do to clean up
+  the failure-before-advancing-nextXid issue, but that is a separate
+  change that will need to be back-patched.  So for the moment I just
+  want to make GetNewTransactionId look the same as it did in prior
+  versions.
+  <a href="http://git.postgresql.org/pg/commitdiff/d2088ae949993ad8e3aabc3b6a9cd77aa5cac957">http://git.postgresql.org/pg/commitdiff/d2088ae949993ad8e3aabc3b6a9cd77aa5cac957</a>
+</p>
+
+<p>
+- Fix some portability issues in isolation regression test driver.
+  Remove random system #includes in favor of using postgres_fe.h.
+  (The alternative to that is letting this module grow its own
+  configuration testing ability...) Also fix the "make clean" target
+  to actually clean things up.  Per local testing.
+  <a href="http://git.postgresql.org/pg/commitdiff/eff223ffd74eed268f35d693462969f7f75632d2">http://git.postgresql.org/pg/commitdiff/eff223ffd74eed268f35d693462969f7f75632d2</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Small cleanup of spacing in verbatim DocBook elements
+  <a href="http://git.postgresql.org/pg/commitdiff/4b08bf8ce7a7515f669ce0a1ce1946c6492b65ed">http://git.postgresql.org/pg/commitdiff/4b08bf8ce7a7515f669ce0a1ce1946c6492b65ed</a>
+</p>
+
+<p>
+- Fix alignment of --help output.  Tabs replaced by spaces.
+  <a href="http://git.postgresql.org/pg/commitdiff/ce2fc20071a6ae68e63bd675b147818669cd83b4">http://git.postgresql.org/pg/commitdiff/ce2fc20071a6ae68e63bd675b147818669cd83b4</a>
+</p>
+
+<p>
+- Message style cleanup
+  <a href="http://git.postgresql.org/pg/commitdiff/bff074b1ab0dfed7a7822dcc8942f877efa3b914">http://git.postgresql.org/pg/commitdiff/bff074b1ab0dfed7a7822dcc8942f877efa3b914</a>
+</p>
+
+<p>
+- Remove redundant port number check.  pg_basebackup doesn't need to
+  police the format of port numbers.  libpq already does that.
+  <a href="http://git.postgresql.org/pg/commitdiff/7f1f1bfdbb199a003b9bef5dc946eb2c1c38e4c2">http://git.postgresql.org/pg/commitdiff/7f1f1bfdbb199a003b9bef5dc946eb2c1c38e4c2</a>
+</p>
+
+<p>
+- Link some tables into the surrounding text by their id
+  <a href="http://git.postgresql.org/pg/commitdiff/a3b681f0bc46de6ae89c7e17c1704329ffc3ba76">http://git.postgresql.org/pg/commitdiff/a3b681f0bc46de6ae89c7e17c1704329ffc3ba76</a>
+</p>
+
+<p>
+- Improve pg_archivecleanup and pg_standby --help output.  For
+  consistency with other tools, put the options before further usage
+  information.  In pg_standby, remove the supposedly deprecated -l
+  option from the given example invocation.
+  <a href="http://git.postgresql.org/pg/commitdiff/b24181b26fc90758370e475088be4ef2497d3cc3">http://git.postgresql.org/pg/commitdiff/b24181b26fc90758370e475088be4ef2497d3cc3</a>
+</p>
+
+<p>
+- Improve formatting of pg_upgrade --help output.
+  <a href="http://git.postgresql.org/pg/commitdiff/d6d823c8b0e6878cf532120c0c019c7704b27be3">http://git.postgresql.org/pg/commitdiff/d6d823c8b0e6878cf532120c0c019c7704b27be3</a>
+</p>
+
+<p>
+- Improve compiler string shown in version().  With some compilers
+  such as Clang and ICC emulating GCC, using a version string of the
+  form "GCC $version" can be quite misleading.  Also, a great while
+  ago, the version output from gcc --version started including the
+  string "gcc", so it is redundant to repeat that.  In order to
+  support ancient GCC versions, we now prefix the result with "GCC "
+  only if the version output does not start with a letter.
+  <a href="http://git.postgresql.org/pg/commitdiff/8dd2ede3f82505c3fd041c1953524305df0732d1">http://git.postgresql.org/pg/commitdiff/8dd2ede3f82505c3fd041c1953524305df0732d1</a>
+</p>
+
+<p>
+Alvaro Herrera pushed:
+</p>
+
+<p>
+- Update some ALTER USER cross-references to ALTER ROLE.  Greg Smith
+  <a href="http://git.postgresql.org/pg/commitdiff/52897e54db1000f2fa45b31e02eb252dd0573516">http://git.postgresql.org/pg/commitdiff/52897e54db1000f2fa45b31e02eb252dd0573516</a>
+</p>
+
+<p>
+- Add ID attribute to some sect2's missing it.  David Fetter
+  <a href="http://git.postgresql.org/pg/commitdiff/155743ad3108cd586d56e864d1209b82f9a716f0">http://git.postgresql.org/pg/commitdiff/155743ad3108cd586d56e864d1209b82f9a716f0</a>
+</p>
+
+<p>
+- Update obsolete mention of Sequoia, now known as Tungsten.  Per
+  <a href="http://joomla.aws.continuent.com/community/lab-projects/sequoia">http://joomla.aws.continuent.com/community/lab-projects/sequoia</a> Greg
+  Smith
+  <a href="http://git.postgresql.org/pg/commitdiff/04be7ac271c4b6db6ba518225f58f936b3b4435c">http://git.postgresql.org/pg/commitdiff/04be7ac271c4b6db6ba518225f58f936b3b4435c</a>
+</p>
+
+<p>
+- Improve description of read/write traffic scalability.  Greg Smith,
+  after a suggestion of James Bruce
+  <a href="http://git.postgresql.org/pg/commitdiff/561485709673f4bc05240e891dd9056bdedbbcbc">http://git.postgresql.org/pg/commitdiff/561485709673f4bc05240e891dd9056bdedbbcbc</a>
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Improve style of generate_history.pl Perl script.
+  <a href="http://git.postgresql.org/pg/commitdiff/fb3ad7895ece674fc5298df754253f70cda6a02e">http://git.postgresql.org/pg/commitdiff/fb3ad7895ece674fc5298df754253f70cda6a02e</a>
+</p>
+
+<p>
+- Adjust pg_upgrade FATAL error messages to have consistent newlines.
+  Also adjust some error message capitalization for consistency.
+  <a href="http://git.postgresql.org/pg/commitdiff/5c5f83507cb697e436f8f9d20d62787c1a66d19c">http://git.postgresql.org/pg/commitdiff/5c5f83507cb697e436f8f9d20d62787c1a66d19c</a>
+</p>
+
+<p>
+- Check that the pg_upgrade user specified is a super-user.  Also
+  report the error message when the post-pg_ctl connection fails.  Per
+  private bug report from EnterpriseDB.
+  <a href="http://git.postgresql.org/pg/commitdiff/81301b85781245676f874ae3908015f05d3aaaa2">http://git.postgresql.org/pg/commitdiff/81301b85781245676f874ae3908015f05d3aaaa2</a>
+</p>
+
+<p>
+- In pg_upgrade, report non-super-user username in error message.
+  <a href="http://git.postgresql.org/pg/commitdiff/1609ca5adb5c8b55076435094532dfbb2a2aea43">http://git.postgresql.org/pg/commitdiff/1609ca5adb5c8b55076435094532dfbb2a2aea43</a>
+</p>
+
+<p>
+- Add missing documention connecting word.
+  <a href="http://git.postgresql.org/pg/commitdiff/5293de580734bb16c57de51142354d76347a3336">http://git.postgresql.org/pg/commitdiff/5293de580734bb16c57de51142354d76347a3336</a>
+</p>
+
+<p>
+- Add xreflabels to /contrib manuals so links appear correct.  Also
+  update README.links to explain xref properly.
+  <a href="http://git.postgresql.org/pg/commitdiff/e567c9ff3409203a3ab50a2ff87cdab73bef6313">http://git.postgresql.org/pg/commitdiff/e567c9ff3409203a3ab50a2ff87cdab73bef6313</a>
+</p>
+
+<p>
+- Add C comment why client encoding can be set in pg_upgrade.
+  <a href="http://git.postgresql.org/pg/commitdiff/e6a740284291d1ebaca42b2954eb20e09daac9b9">http://git.postgresql.org/pg/commitdiff/e6a740284291d1ebaca42b2954eb20e09daac9b9</a>
+</p>
+
+<p>
+- Add C comment about the fact that the autovacuum limit can go
+  backwards by 3, but that is it OK.
+  <a href="http://git.postgresql.org/pg/commitdiff/76e5b4c85d5d4830888044fc885b1da0d781aed0">http://git.postgresql.org/pg/commitdiff/76e5b4c85d5d4830888044fc885b1da0d781aed0</a>
+</p>
+
+<p>
+Magnus Hagander pushed:
+</p>
+
+<p>
+- Clarify error message when attempting to create index on foreign
+  table.  Instead of just saying "is not a table", specifically state
+  that indexes aren't supported on *foreign* tables.
+  <a href="http://git.postgresql.org/pg/commitdiff/d76a149c955a6525c8d42425c57e32d74d2c2eed">http://git.postgresql.org/pg/commitdiff/d76a149c955a6525c8d42425c57e32d74d2c2eed</a>
+</p>
+
+<p>
+- Unbreak the regression tests from my previous commit
+  <a href="http://git.postgresql.org/pg/commitdiff/27525b183189487c674f24620e608298ac0c8e29">http://git.postgresql.org/pg/commitdiff/27525b183189487c674f24620e608298ac0c8e29</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Fix typos in SECURITY LABEL documentation.  KaiGai Kohei
+  <a href="http://git.postgresql.org/pg/commitdiff/3ef5b2df9738fd0795c1ffcaada93c3c5df7cd49">http://git.postgresql.org/pg/commitdiff/3ef5b2df9738fd0795c1ffcaada93c3c5df7cd49</a>
+</p>
+
+<p>
+- Add comment about memory reordering to PredicateLockTupleRowVersionLink.
+  Dan Ports, per head-scratching from Simon Riggs and myself.
+  <a href="http://git.postgresql.org/pg/commitdiff/71932ecc2b6ca0d748176a7e8b11d3575bf4caf3">http://git.postgresql.org/pg/commitdiff/71932ecc2b6ca0d748176a7e8b11d3575bf4caf3</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Gabriele Bartolini sent in another revision of the patch to smooth
+replication during VACUUM FULL.
+</p>
+
+<p>
+Joe Conway sent in a patch to fix clog redos under high load.
+</p>
+
+<p>
+Johann 'Myrkraverk' Oskarsson sent in a patch to fix an issue on
+mingw-w64 where the PGDLLEXPORT macro is blank.
+</p>
+
+<p>
+Alvaro Herrera updated the "preferred types" patch to HEAD.
+</p>
+
+<p>
+Jaime Casanova sent in a patch to add an xlogversion column to
+IDENTIFY_SYSTEM.  This is one of the infrastructure pieces which will
+make on-line upgrades possible.
+</p>
+
+<p>
+Hitoshi Harada sent in a patch to allow the optimizer to pull up
+aggregate subqueries.
+</p>
+
+<p>
+Bruce Momjian sent in patches to adjust the comments on system tables.
+</p>
+
+<p>
+Magnus Hagander sent in a patch to fix the error for attempting to
+index a foreign table.
+</p>
+
+<p>
+Tom Lane sent in a patch to fix a some suprising precedence in
+PostgreSQL's SQL grammar.
+</p>
+
+<p>
+Dan Ports sent in two revisions of a patch to fix a race condition in
+SSI's ChecTargetForConflictsIn.
+</p>
+
+<p>
+Peter Geoghegan sent in a WIP patch to help save energy by waking up
+less frequently.
+</p>
+
+<p>
+Merlin Moncure sent in another revision of the patch to fix an issue
+between the visibility map and hint bits.
+</p>
+
+<p>
+Robert Haas sent in another revision of the patch to make visibility
+maps more crash-safe.
+</p>
+
+<p>
+Josh Kupershmidt sent in a patch to clean up psql's decribe.c.
+</p>
+
+<p>
+Andrew Dunstan sent in another revision of the patch to fix an issue
+where invalid characters were allowed in XML.
+</p>
+
+<p>
+Greg Smith sent in a patch exemplifying the idea of moving some
+contrib modules to being default, but still using the EXTENSION
+infrastructure.
+
+</p>
+