From: David Fetter <david@fetter.org>
Date: Mon, 21 Mar 2011 05:07:55 +0000 (+0000)
Subject: PostgreSQL Weekly News March 20, 2011
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=8725dda53c5e74fb1678230ca3c75403908262f1;p=pgweb-old.git

PostgreSQL Weekly News March 20, 2011

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

diff --git a/portal/files/weeklynews.xml b/portal/files/weeklynews.xml
index 747644c8..cca0f940 100644
--- a/portal/files/weeklynews.xml
+++ b/portal/files/weeklynews.xml
@@ -10,6 +10,42 @@
 <description></description>
 <language>en</language>
 
+<item>
+<title>PostgreSQL Weekly News March 20th 2011</title>
+<description>
+PostgreSQL was accepted as a mentoring organization for Google Summer
+of Code 2011!  If you are a student interested in applying,
+applications open March 28, 2011.  Details and ideas for projects here:
+&#x3C;a href=&#x22;http://wiki.postgresql.org/wiki/GSoC_2011&#x22;&#x3E;http://wiki.postgresql.org/wiki/GSoC_2011&#x3C;/a&#x3E;
+
+
+</description>
+<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110320</guid>
+<pubDate>Sun, 20 Mar 2011 00:00:00 PST</pubDate>
+</item>
+<item>
+<title>PostgreSQL Weekly News March 13th 2011</title>
+<description>
+PostgreSQL 9.1alpha4 released, with lots of big, new goodies!
+This is the last planned alpha for 9.1.  You can get it here:
+&#x3C;a href=&#x22;http://www.postgresql.org/developer/alpha&#x22;&#x3E;http://www.postgresql.org/developer/alpha&#x3C;/a&#x3E;
+
+
+</description>
+<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>
 <item>
 <title>PostgreSQL Weekly News February 27th 2011</title>
 <description>
@@ -90,41 +126,5 @@ The final commitfest of 9.1 has begun.  Start reviewing those patches!
 <guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110116</guid>
 <pubDate>Sun, 16 Jan 2011 00:00:00 PST</pubDate>
 </item>
-<item>
-<title>PostgreSQL Weekly News January 9th 2011</title>
-<description>
-AustinPUG will be meeting this Wednesday, Jan. 12.  The topic will be
-setting up streaming replication.  Free pizza!  RSVP to austinpug AT
-postgresql DOT org appreciated but not required.
-&#x3C;a href=&#x22;http://pugs.postgresql.org/austinpug&#x22;&#x3E;http://pugs.postgresql.org/austinpug&#x3C;/a&#x3E;
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110109</guid>
-<pubDate>Sun, 09 Jan 2011 00:00:00 PST</pubDate>
-</item>
-<item>
-<title>PostgreSQL Weekly News January 2nd 2011</title>
-<description>
-PostgreSQL 9.1alpha3 released!  Get it here:
-&#x3C;a href=&#x22;http://developer.postgresql.org/pgdocs/postgres/release-9-1-alpha.html&#x22;&#x3E;http://developer.postgresql.org/pgdocs/postgres/release-9-1-alpha.html&#x3C;/a&#x3E;
-Here&#x27;s how to test it:
-&#x3C;a href=&#x22;http://wiki.postgresql.org/wiki/HowToBetaTest&#x22;&#x3E;http://wiki.postgresql.org/wiki/HowToBetaTest&#x3C;/a&#x3E;
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110102</guid>
-<pubDate>Sun, 02 Jan 2011 00:00:00 PST</pubDate>
-</item>
-<item>
-<title>PostgreSQL Weekly News December 26th 2010</title>
-<description>
-Happy Boxing Day from the PostgreSQL Weekly News!
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20101226</guid>
-<pubDate>Sun, 26 Dec 2010 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 2e62232c..d3b356d3 100644
--- a/portal/template/en/community/weeklynews.html
+++ b/portal/template/en/community/weeklynews.html
@@ -9,6 +9,9 @@ Weekly News
 <p>To receive the Weekly News in your inbox, please subscribe to the <a href="/community/lists/subscribe">pgsql-announce@postgresql.org</a> mailing list.</p>
 
 <ul>
+    <li><a href="/community/weeklynews/pwn20110320">March 20th 2011</a></li>
+    <li><a href="/community/weeklynews/pwn20110313">March 13th 2011</a></li>
+    <li><a href="/community/weeklynews/pwn20110306">March 6th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110227">February 27th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110220">February 20th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110213">February 13th 2011</a></li>
diff --git a/portal/template/en/community/weeklynews/pwn20110306.html b/portal/template/en/community/weeklynews/pwn20110306.html
new file mode 100644
index 00000000..1d93e636
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110306.html
@@ -0,0 +1,666 @@
+<!-- BEGIN page_title_block -->
+Weekly News - March 06 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - March 06 2011</h1>
+
+<p>
+The list of talks and speakers for PGCon 2011 has been released.
+<a href="http://www.pgcon.org/2011/schedule/day_2011-05-19.en.html">http://www.pgcon.org/2011/schedule/day_2011-05-19.en.html</a>
+</p>
+
+<p>
+Selena Deckelmann is organizing a PL developer summit at PgCon.  Help
+make it great!
+<a href="http://www.chesnok.com/daily/2011/02/28/pl-developer-summit-at-pgcon-may-21/">http://www.chesnok.com/daily/2011/02/28/pl-developer-summit-at-pgcon-may-21/</a>
+</p>
+
+<p>
+There is now a Spanish language version of Planet PostgreSQL.
+<a href="http://planeta.postgresql.org.es/">http://planeta.postgresql.org.es/</a>
+</p>
+
+<p>
+A webcast in Spanish for PostgreSQL 9.0 will happen March 9th.
+<a href="http://inicio.helpame.com/inicio/?q=node/3">http://inicio.helpame.com/inicio/?q=node/3</a>
+</p>
+
+<p>
+There will be a large PostgreSQL presence at the MySQL Conference and
+Expo, April 11-14, 2011 in Santa Clara, California.
+<a href="http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql">http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql</a>
+</p>
+
+<h2>PostgreSQL Jobs for March</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+Gabriele Bartolini of ITPUG will present a talk on PostgreSQL 9.0 at Codemotion
+in Rome on Saturday, March 5th, 2011 at 4:10PM.  More information:
+<a href="http://www.codemotion.it/en/">http://www.codemotion.it/en/</a>
+</p>
+
+<p>
+PostgreSQL Conference East 2011: NYC March 22nd - 25th
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<p>
+Open Database Camp will be on May 7-9, 2011 in Sardinia, Italy
+<a href="http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html">http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html</a>
+</p>
+
+<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>
+
+<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>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- PL/Python custom SPI exceptions.  This provides a separate exception
+  class for each error code that the backend defines, as well as the
+  ability to get the SQLSTATE from the exception object.  Jan
+  Urbański, reviewed by Steve Singer
+  <a href="http://git.postgresql.org/pg/commitdiff/474a42473adf9b18417242f1fc0691a857ec578b">http://git.postgresql.org/pg/commitdiff/474a42473adf9b18417242f1fc0691a857ec578b</a>
+</p>
+
+<p>
+- Fix regression tests after PL/Python custom SPI exceptions patch.
+  <a href="http://git.postgresql.org/pg/commitdiff/4b853c879d3c298b7ea7a09fcb74314bc54c37e4">http://git.postgresql.org/pg/commitdiff/4b853c879d3c298b7ea7a09fcb74314bc54c37e4</a>
+</p>
+
+<p>
+- Dump the COLLATABLE attribute in CREATE TYPE This was previously
+  omitted by accident.
+  <a href="http://git.postgresql.org/pg/commitdiff/16143d64513e4dc3c72bad7ae98d3df0b5a23013">http://git.postgresql.org/pg/commitdiff/16143d64513e4dc3c72bad7ae98d3df0b5a23013</a>
+</p>
+
+<p>
+- Additional PL/Python regression test expected file.
+  plpython_subtransaction test needs a separate expected file
+  specifically for Python 2.5.
+  <a href="http://git.postgresql.org/pg/commitdiff/2f363590c17c0e02186efab5fa0b197b82a5b3ae">http://git.postgresql.org/pg/commitdiff/2f363590c17c0e02186efab5fa0b197b82a5b3ae</a>
+</p>
+
+<p>
+- Support for DragonFly BSD.  Mapped to NetBSD, the closest existing
+  match.  (Even though DragonFly BSD is derived from FreeBSD, the
+  shared library version numbering matches NetBSD, and the rest is
+  mostly the same among all BSD variants.) per "Rumko"
+  <a href="http://git.postgresql.org/pg/commitdiff/6094c242d1ee40a08f3138811425d7540e8269e4">http://git.postgresql.org/pg/commitdiff/6094c242d1ee40a08f3138811425d7540e8269e4</a>
+</p>
+
+<p>
+- Add collations to information_schema.usage_privileges.  This is
+  faked information like for domains.
+  <a href="http://git.postgresql.org/pg/commitdiff/091bda0188250c9802cebca066b4ca9e049616e6">http://git.postgresql.org/pg/commitdiff/091bda0188250c9802cebca066b4ca9e049616e6</a>
+</p>
+
+<p>
+- When creating a collation, check that the locales can be loaded.
+  This is the same check that would happen later when the collation is
+  used, but it's friendlier to check the collation already when it is
+  created.
+  <a href="http://git.postgresql.org/pg/commitdiff/4442e1975d3c4c96a0b573b7abd864b0cbe26f9d">http://git.postgresql.org/pg/commitdiff/4442e1975d3c4c96a0b573b7abd864b0cbe26f9d</a>
+</p>
+
+<p>
+- Don't allow CREATE TABLE AS to create a column with invalid
+  collation.  It is possible that an expression ends up with a
+  collatable type but without a collation.  CREATE TABLE AS could then
+  create a table based on that.  But such a column cannot be dumped
+  with valid SQL syntax, so we disallow creating such a column.  per
+  test report from Noah Misch.
+  <a href="http://git.postgresql.org/pg/commitdiff/b9cff97fdf486eca7e563a9696a7391048814d0f">http://git.postgresql.org/pg/commitdiff/b9cff97fdf486eca7e563a9696a7391048814d0f</a>
+</p>
+
+<p>
+- Update of SQL feature conformance.
+  <a href="http://git.postgresql.org/pg/commitdiff/9650364b7b2fc5d676f87cca7b5f9ff991cdb7af">http://git.postgresql.org/pg/commitdiff/9650364b7b2fc5d676f87cca7b5f9ff991cdb7af</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Rename pg_stat_replication.apply_location to replay_location.  For
+  consistency with pg_last_xlog_replay_location.  Per discussion.
+  <a href="http://git.postgresql.org/pg/commitdiff/92c30fd2edee6da6e018f41a1d67b4ac2f8fcbdd">http://git.postgresql.org/pg/commitdiff/92c30fd2edee6da6e018f41a1d67b4ac2f8fcbdd</a>
+</p>
+
+<p>
+- Avoid excessive Hot Standby feedback messages.  Without this patch,
+  when wal_receiver_status_interval=0, indicating that no status
+  messages should be sent, Hot Standby feedback messages are instead
+  sent extremely frequently.  Fujii Masao, with documentation changes
+  by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/59d6a7594288ebc909a24f3fc9e502f097bbe2ff">http://git.postgresql.org/pg/commitdiff/59d6a7594288ebc909a24f3fc9e502f097bbe2ff</a>
+</p>
+
+<p>
+- Refactor seclabel.c to use the new check_object_ownership function.
+  This avoids duplicate (and not-quite-matching) code, and makes the
+  logic for SECURITY LABEL match COMMENT and ALTER EXTENSION ADD/DROP.
+  <a href="http://git.postgresql.org/pg/commitdiff/efa415da8c0fb8c1c0bc50faebac430f8b917571">http://git.postgresql.org/pg/commitdiff/efa415da8c0fb8c1c0bc50faebac430f8b917571</a>
+</p>
+
+<p>
+- Remove emphasis from 9.1alpha3 items.  In preparation for 9.1alpha4
+  release notes, where only the 9.1alpha4 features will be emphasized.
+  <a href="http://git.postgresql.org/pg/commitdiff/a4406da967093a9793db0fbceb6e226e318932b6">http://git.postgresql.org/pg/commitdiff/a4406da967093a9793db0fbceb6e226e318932b6</a>
+</p>
+
+<p>
+- First cut at 9.1alpha4 release notes.
+  <a href="http://git.postgresql.org/pg/commitdiff/5c44f38d3b63c5a11f58fe558adfe4d3cf4dcc39">http://git.postgresql.org/pg/commitdiff/5c44f38d3b63c5a11f58fe558adfe4d3cf4dcc39</a>
+</p>
+
+<p>
+- Add missing word.
+  <a href="http://git.postgresql.org/pg/commitdiff/f31e532492aa950c62c3ded32d07d1e42017e557">http://git.postgresql.org/pg/commitdiff/f31e532492aa950c62c3ded32d07d1e42017e557</a>
+</p>
+
+<p>
+- Remove one copy of duplicated alpha4 release note.  Noted by Andy
+  Colson.
+  <a href="http://git.postgresql.org/pg/commitdiff/c0f2b2e256a3e98c2a066cee8623b7ab156b7f9c">http://git.postgresql.org/pg/commitdiff/c0f2b2e256a3e98c2a066cee8623b7ab156b7f9c</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Unbreak vpath builds broken by commit 474a42473adf9b18417242f1fc0691a857ec578b.
+  <a href="http://git.postgresql.org/pg/commitdiff/57e9bda5ec6a032e1e6d51dad5e534a11669c6bf">http://git.postgresql.org/pg/commitdiff/57e9bda5ec6a032e1e6d51dad5e534a11669c6bf</a>
+</p>
+
+<p>
+- Fix plpython breakage detected on certain Fedora machines on
+  buildfarm.  Patch from Jan Urbański.
+  <a href="http://git.postgresql.org/pg/commitdiff/4c966d920fb75a5d0366b887c2ef28e6d87c1eda">http://git.postgresql.org/pg/commitdiff/4c966d920fb75a5d0366b887c2ef28e6d87c1eda</a>
+</p>
+
+<p>
+- Add a comment explaining the recent fix for plpython breakage in
+  commit 4c966d9.  Mostly text supplied by Jan Urbański.
+  <a href="http://git.postgresql.org/pg/commitdiff/12bf602f3fe963a9d155778b9385186c3a0b5ed3">http://git.postgresql.org/pg/commitdiff/12bf602f3fe963a9d155778b9385186c3a0b5ed3</a>
+</p>
+
+<p>
+- Add PL extension files to MSVC Install procedure.
+  <a href="http://git.postgresql.org/pg/commitdiff/a956b160261579ae2422b539ccf73d75684351fb">http://git.postgresql.org/pg/commitdiff/a956b160261579ae2422b539ccf73d75684351fb</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Rearrange snapshot handling to make rule expansion more consistent.
+  With this patch, portals, SQL functions, and SPI all agree that
+  there should be only a CommandCounterIncrement between the queries
+  that are generated from a single SQL command by rule expansion.
+  Fetching a whole new snapshot now happens only between original
+  queries.  This is equivalent to the existing behavior of EXPLAIN
+  ANALYZE, and it was judged to be the best choice since it eliminates
+  one source of concurrency hazards for rules.  The patch should also
+  make things marginally faster by reducing the number of snapshot
+  push/pop operations.  The patch removes pg_parse_and_rewrite(),
+  which is no longer used anywhere.  There was considerable discussion
+  about more aggressive refactoring of the query-processing functions
+  exported by postgres.c, but for the moment nothing more has been
+  done there.  I also took the opportunity to refactor snapmgr.c's API
+  slightly: the former PushUpdatedSnapshot() has been split into two
+  functions.  Marko Tiikkaja, reviewed by Steve Singer and Tom Lane.
+  <a href="http://git.postgresql.org/pg/commitdiff/c0b00760365c74308e9e0719c993eadfbcd090c2">http://git.postgresql.org/pg/commitdiff/c0b00760365c74308e9e0719c993eadfbcd090c2</a>
+</p>
+
+<p>
+- Update discussion of EXPLAIN to reflect existence of ModifyTable
+  nodes.  Back-patch to 9.0, since this was changed then.
+  <a href="http://git.postgresql.org/pg/commitdiff/09b49a8439fde63826f93f55430868cf2585644b">http://git.postgresql.org/pg/commitdiff/09b49a8439fde63826f93f55430868cf2585644b</a>
+</p>
+
+<p>
+- Include the target table in EXPLAIN output for ModifyTable nodes.
+  Per discussion, this seems important for plans involving writable
+  CTEs, since there can now be more than one ModifyTable node in the
+  plan.  To retain the same formatting as for target tables of scan
+  nodes, we show only one target table, which will be the parent table
+  in case of an UPDATE or DELETE on an inheritance tree.  Individual
+  child tables can be determined by inspecting the child plan trees if
+  needed.
+  <a href="http://git.postgresql.org/pg/commitdiff/97c4ee94adf15f7a0a39cbb5549159e2aa0679d1">http://git.postgresql.org/pg/commitdiff/97c4ee94adf15f7a0a39cbb5549159e2aa0679d1</a>
+</p>
+
+<p>
+- Correct mistaken claims about EXPLAIN ANALYZE's handling of
+  triggers.  Time spent executing AFTER triggers is not included in
+  the runtime of the associated ModifyTable node; in my patch of
+  yesterday I confused queuing of these triggers with their actual
+  execution.  Spotted by Marko Tiikkaja.
+  <a href="http://git.postgresql.org/pg/commitdiff/7e49330cad885a76441253da74b88e7d2f27c9f0">http://git.postgresql.org/pg/commitdiff/7e49330cad885a76441253da74b88e7d2f27c9f0</a>
+</p>
+
+<p>
+- Fix erroneous documentation of the syntax of CREATE CONSTRAINT
+  TRIGGER.  The grammar requires a specific ordering of the clauses,
+  but the documentation showed a different order.  This error was
+  introduced in commit b47953f9c69d48a9261bd643e3170017b93f6337, which
+  merged the CREATE CONSTRAINT TRIGGER documentation into the CREATE
+  TRIGGER page.  There is no code bug AFAICS.
+  <a href="http://git.postgresql.org/pg/commitdiff/2f6c8453cf3f38a70adbcb59489630cd5be92570">http://git.postgresql.org/pg/commitdiff/2f6c8453cf3f38a70adbcb59489630cd5be92570</a>
+</p>
+
+<p>
+- Add KNNGIST support to contrib/btree_gist.  This extends GiST's
+  support for nearest-neighbor searches to many of the standard data
+  types.  Teodor Sigaev
+  <a href="http://git.postgresql.org/pg/commitdiff/8436489c81c23af637696ac69cdaafddcc907ee1">http://git.postgresql.org/pg/commitdiff/8436489c81c23af637696ac69cdaafddcc907ee1</a>
+</p>
+
+<p>
+- Add 'collatable' to the Parameters section of CREATE TYPE.
+  <a href="http://git.postgresql.org/pg/commitdiff/43bdf3583a9a5912e1800ab140b8ca495ae69d85">http://git.postgresql.org/pg/commitdiff/43bdf3583a9a5912e1800ab140b8ca495ae69d85</a>
+</p>
+
+<p>
+- Mark operator implementation functions as such in their comments.
+  Historically, we've not had separate comments for built-in
+  pg_operator entries, but relied on the comments for the underlying
+  functions.  The trouble with this approach is that there isn't much
+  of anything to suggest to users that they'd be better off using the
+  operators instead.  So, move all the relevant comments into
+  pg_operator, and give each underlying function a comment that just
+  says "implementation of XXX operator".  There are only about half a
+  dozen cases where it seems reasonable to use the underlying function
+  interchangeably with the operator; in these cases I left the same
+  comment in place on the function as on the operator.  While at it,
+  establish a policy that every built-in function and operator entry
+  should have a comment: there are now queries in the opr_sanity
+  regression test that will complain if one doesn't.  This only
+  required adding a dozen or two more entries than would have been
+  there anyway.  I also spent some time trying to eliminate gratuitous
+  inconsistencies in the style of the comments, though it's hopeless
+  to suppose that more won't creep in soon enough.  Per my proposal of
+  2010-10-15.
+  <a href="http://git.postgresql.org/pg/commitdiff/94133a935414407920a47d06a6e22734c974c3b8">http://git.postgresql.org/pg/commitdiff/94133a935414407920a47d06a6e22734c974c3b8</a>
+</p>
+
+<p>
+- Add -lm to SHLIB_LINK for contrib/btree_gist.  Now that btree_gist
+  contains a reference to isinf(), this is necessary at least on some
+  platforms.  Per buildfarm.
+  <a href="http://git.postgresql.org/pg/commitdiff/8c4164540b30434845be02f84973663bfeb231ab">http://git.postgresql.org/pg/commitdiff/8c4164540b30434845be02f84973663bfeb231ab</a>
+</p>
+
+<p>
+- Run a portal's cleanup hook immediately when pushing it to DONE
+  state.  This works around the problem noted by Yamamoto Takashi in
+  bug #5906, that there were code paths whereby we could reach
+  AtCleanup_Portals with a portal's cleanup hook still unexecuted.
+  The changes I made a few days ago were intended to prevent that from
+  happening, and I think that on balance it's still a good thing to
+  avoid, so I don't want to remove the Assert in AtCleanup_Portals.
+  Hence do this instead.
+  <a href="http://git.postgresql.org/pg/commitdiff/6252c4f9e201f619e5eebda12fa867acd4e4200e">http://git.postgresql.org/pg/commitdiff/6252c4f9e201f619e5eebda12fa867acd4e4200e</a>
+</p>
+
+<p>
+- Fix citext's upgrade-from-unpackaged script to set its collation
+  correctly.  Although there remains some debate about how CREATE TYPE
+  should represent the collation property, this doesn't really affect
+  what we need to do in citext's script, so go ahead and fix that.
+  <a href="http://git.postgresql.org/pg/commitdiff/94be9e3f0ca9e7ced66168397eb586565bced9ca">http://git.postgresql.org/pg/commitdiff/94be9e3f0ca9e7ced66168397eb586565bced9ca</a>
+</p>
+
+<p>
+- Further refine patch for commenting operator implementation
+  functions.  Instead of manually maintaining the "implementation of
+  XXX operator" comments in pg_proc.h, delete all those entries and
+  let initdb create them via a join.  To let initdb figure out which
+  name to use when there is a conflict, change the comments for
+  deprecated operators to say they are deprecated --- which seems like
+  a good thing to do anyway.
+  <a href="http://git.postgresql.org/pg/commitdiff/908ab80286401bb20a519fa7dc7a837631f20369">http://git.postgresql.org/pg/commitdiff/908ab80286401bb20a519fa7dc7a837631f20369</a>
+</p>
+
+<p>
+- In initialize_SSL, don't fail unnecessarily when home dir is
+  unavailable.  Instead, just act as though the certificate file(s)
+  are not present.  There is only one case where this need be a hard
+  failure condition: when sslmode is verify-ca or verify-full, not
+  having a root cert file is an error.  Change the logic so that we
+  complain only in that case, and otherwise fall through cleanly.
+  This is how it used to behave pre-9.0, but my patch
+  4ed4b6c54e5fab24ab2624d80e26f7546edc88ad of 2010-05-26 broke the
+  case.  Per report from Christian Kastner.
+  <a href="http://git.postgresql.org/pg/commitdiff/bd58d9d883111ee84de4af480ebb018fe9b0bf27">http://git.postgresql.org/pg/commitdiff/bd58d9d883111ee84de4af480ebb018fe9b0bf27</a>
+</p>
+
+<p>
+- Allow non-superusers to create (some) extensions.  Remove the
+  unconditional superuser permissions check in CREATE EXTENSION, and
+  instead define a "superuser" extension property, which when false
+  (not the default) skips the superuser permissions check.  In this
+  case the calling user only needs enough permissions to execute the
+  commands in the extension's installation script.  The superuser
+  property is also enforced in the same way for ALTER EXTENSION UPDATE
+  cases.  In other ALTER EXTENSION cases and DROP EXTENSION, test
+  ownership of the extension rather than superuserness.  ALTER
+  EXTENSION ADD/DROP needs to insist on ownership of the target object
+  as well; to do that without duplicating code, refactor comment.c's
+  big switch for permissions checks into a separate function in
+  objectaddress.c.  I also removed the superuserness checks in
+  pg_available_extensions and related functions; there's no strong
+  reason why everybody shouldn't be able to see that info.  Also
+  invent an IF NOT EXISTS variant of CREATE EXTENSION, and use that in
+  pg_dump, so that dumps won't fail for installed-by-default
+  extensions.  We don't have any of those yet, but we will soon.  This
+  is all per discussion of wrapping the standard procedural languages
+  into extensions.  I'll make those changes in a separate commit; this
+  is just putting the core infrastructure in place.
+  <a href="http://git.postgresql.org/pg/commitdiff/8d3b421f5f7b955e7ac7d156aa74ee6a6fe4e9f6">http://git.postgresql.org/pg/commitdiff/8d3b421f5f7b955e7ac7d156aa74ee6a6fe4e9f6</a>
+</p>
+
+<p>
+- Create extension infrastructure for the core procedural languages.
+  This mostly just involves creating control, install, and
+  update-from-unpackaged scripts for them.  However, I had to adjust
+  plperl and plpython to not share the same support functions between
+  variants, because we can't put the same function into multiple
+  extensions.  catversion bump forced due to new contents of
+  pg_pltemplate, and because initdb now installs plpgsql as an
+  extension not a bare language.  Add support for regression testing
+  these as extensions not bare languages.  Fix a couple of other
+  issues that popped up while testing this: my initial hack at pg_dump
+  binary-upgrade support didn't work right, and we don't want an extra
+  schema permissions test after all.  Documentation changes still to
+  come, but I'm committing now to see whether the MSVC build scripts
+  need work (likely they do).
+  <a href="http://git.postgresql.org/pg/commitdiff/63b656b7bf39beb5b6095ab2b5e1e4e9d8c6a965">http://git.postgresql.org/pg/commitdiff/63b656b7bf39beb5b6095ab2b5e1e4e9d8c6a965</a>
+</p>
+
+<p>
+- Update documentation to reflect that standard PLs are now
+  extensions.  Recommend use of CREATE EXTENSION rather than plain
+  CREATE LANGUAGE where relevant.  Encourage PL authors to provide
+  extension wrappers for their PLs.
+  <a href="http://git.postgresql.org/pg/commitdiff/c2903fb3d2aeb0a7206945478ad28bc47bd6c6e8">http://git.postgresql.org/pg/commitdiff/c2903fb3d2aeb0a7206945478ad28bc47bd6c6e8</a>
+</p>
+
+<p>
+- Convert createlang/droplang to use CREATE/DROP EXTENSION.  In
+  createlang this is a one-line change.  In droplang there's a whole
+  lot of cruft that can be discarded since the extension mechanism now
+  manages removal of the language's support functions.  Also, add
+  deprecation notices to these two programs' reference pages, since
+  per discussion we may toss them overboard altogether in a release or
+  two.
+  <a href="http://git.postgresql.org/pg/commitdiff/ba0c93a0f46ca70cae47a8817067c1e98482979f">http://git.postgresql.org/pg/commitdiff/ba0c93a0f46ca70cae47a8817067c1e98482979f</a>
+</p>
+
+<p>
+- Make plpythonu language use plpython2 shared library directly.  The
+  original scheme for this was to symlink plpython.$DLSUFFIX to
+  plpython2.$DLSUFFIX, but that doesn't work on Windows, and only
+  accidentally failed to fail because of the way that CREATE LANGUAGE
+  created or didn't create new C functions.  My changes of yesterday
+  exposed the weakness of that approach.  To fix, get rid of the
+  symlink and make pg_pltemplate show what's really going on.
+  <a href="http://git.postgresql.org/pg/commitdiff/bfd7f8cbb2ddf8c48ac310a80d33c951087c12c4">http://git.postgresql.org/pg/commitdiff/bfd7f8cbb2ddf8c48ac310a80d33c951087c12c4</a>
+</p>
+
+<p>
+- Adjust documentation about pg_pltemplate to reflect latest thinking.
+  It's more likely that pg_pltemplate will go away in the future than
+  that we'll add additional specialized infrastructure for it.
+  <a href="http://git.postgresql.org/pg/commitdiff/0b5d7345925dd0212d4509195a337f1912781af1">http://git.postgresql.org/pg/commitdiff/0b5d7345925dd0212d4509195a337f1912781af1</a>
+</p>
+
+<p>
+- Fix incorrect access to pg_index.indcollation.  Since this field is
+  after a variable-length field, it can't simply be accessed via the C
+  struct for pg_index.  Fortunately, the relcache already did the
+  dirty work of pulling the information out to where it can be
+  accessed easily, so this is a one-line fix.  Andres Freund
+  <a href="http://git.postgresql.org/pg/commitdiff/149b2673c244b92b59411dd2292d6ddcfb03d5d4">http://git.postgresql.org/pg/commitdiff/149b2673c244b92b59411dd2292d6ddcfb03d5d4</a>
+</p>
+
+<p>
+- Fix pg_dump's dump order for collations versus extensions.  Mixing
+  them together alphabetically won't be nice.  Per my gripe of
+  2011-02-12.
+</p>
+
+<p>
+- Add missing "static" marker to internal_ping().  Per testing with a
+  compiler that doesn't like that.
+  <a href="http://git.postgresql.org/pg/commitdiff/775464e8450677602833b1d11b919838e7b2b29a">http://git.postgresql.org/pg/commitdiff/775464e8450677602833b1d11b919838e7b2b29a</a>
+</p>
+
+<p>
+- Fix a couple more missing "static" markers.
+  <a href="http://git.postgresql.org/pg/commitdiff/dfe18f18d262df731378cbf38a4136f08ca119a5">http://git.postgresql.org/pg/commitdiff/dfe18f18d262df731378cbf38a4136f08ca119a5</a>
+</p>
+
+<p>
+- Suppress some "variable might be clobbered by longjmp" warnings.
+  Seen with an older gcc version.  I'm not sure these represent any
+  real risk factor, but still a bit scary.  Anyway we have lots of
+  other volatile-marked variables in this code, so a couple more won't
+  hurt.
+  <a href="http://git.postgresql.org/pg/commitdiff/4172bd88300524efd1728c247fbc1eff3c1ca6ed">http://git.postgresql.org/pg/commitdiff/4172bd88300524efd1728c247fbc1eff3c1ca6ed</a>
+</p>
+
+<p>
+Heikki Linnakangas pushed:
+</p>
+
+<p>
+- Fix bugs in Serializable Snapshot Isolation.  Change the way UPDATEs
+  are handled. Instead of maintaining a chain of tuple-level locks in
+  shared memory, copy any existing locks on the old tuple to the new
+  tuple at UPDATE. Any existing page-level lock needs to be duplicated
+  too, as a lock on the new tuple. That was neglected previously.
+  Store xmin on tuple-level predicate locks, to distinguish a lock on
+  an old already-recycled tuple from a new tuple at the same physical
+  location.  Failure to distinguish them caused loops in the
+  tuple-lock chains, as reported by YAMAMOTO Takashi. Although we
+  don't use the chain representation of UPDATEs anymore, it seems like
+  a good idea to store the xmin to avoid some false positives if no
+  other reason.  CheckSingleTargetForConflictsIn now correctly handles
+  the case where a lock that's being held is not reflected in the
+  local lock table. That happens if another backend acquires a lock on
+  our behalf due to an UPDATE or a page split.
+  PredicateLockPageCombine now retains locks for the page that is
+  being removed, rather than removing them. This prevents a
+  potentially dangerous false-positive inconsistency where the local
+  lock table believes that a lock is held, but it is actually not.
+  Dan Ports and Kevin Grittner
+  <a href="http://git.postgresql.org/pg/commitdiff/47ad79122bc099c1f0ea8a7ae413fcd8d45e26a6">http://git.postgresql.org/pg/commitdiff/47ad79122bc099c1f0ea8a7ae413fcd8d45e26a6</a>
+</p>
+
+<p>
+- Change pg_last_xlog_receive_location() not to move backwards. That
+  makes it a lot more useful for determining which standby is most
+  up-to-date, for example. There was long discussions on whether
+  overwriting existing existing WAL makes sense to begin with, and
+  whether we should do some more extensive variable renaming, but this
+  change nevertheless seems quite uncontroversial.  Fujii Masao,
+  reviewed by Jeff Janes, Robert Haas, Stephen Frost.
+  <a href="http://git.postgresql.org/pg/commitdiff/6eba5a7c57d1d61f46b6966026bf7bc07f8e087c">http://git.postgresql.org/pg/commitdiff/6eba5a7c57d1d61f46b6966026bf7bc07f8e087c</a>
+</p>
+
+<p>
+- Add tab-completion for table name after JOIN.  Andrey Popp
+  <a href="http://git.postgresql.org/pg/commitdiff/8e2d8b1497ac64142bb7df05e39a58ebf3e62bf6">http://git.postgresql.org/pg/commitdiff/8e2d8b1497ac64142bb7df05e39a58ebf3e62bf6</a>
+</p>
+
+<p>
+- You must hold a lock on the heap page when you call
+  CheckForSerializableConflictOut(), because it can set hint bits.
+  YAMAMOTO Takashi
+  <a href="http://git.postgresql.org/pg/commitdiff/ee3838b1d35cffec21ca40dbfc409ec40ddf3e28">http://git.postgresql.org/pg/commitdiff/ee3838b1d35cffec21ca40dbfc409ec40ddf3e28</a>
+</p>
+
+<p>
+Michael Meskes pushed:
+</p>
+
+<p>
+- Added new version of ecpg's parser generator script.  This one was
+  written by Andy Colson.
+  <a href="http://git.postgresql.org/pg/commitdiff/32fce70564999a90d48a27c4279a8908e90f3ece">http://git.postgresql.org/pg/commitdiff/32fce70564999a90d48a27c4279a8908e90f3ece</a>
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Fix parallel gmake for extension directory addition in PL languages.
+  <a href="http://git.postgresql.org/pg/commitdiff/c15c1f1c15fc19d20c0699aeb312664f5529c87a">http://git.postgresql.org/pg/commitdiff/c15c1f1c15fc19d20c0699aeb312664f5529c87a</a>
+</p>
+
+<p>
+- Print clearer failure message when pg_upgrade fails due to a fatal
+  error.
+  <a href="http://git.postgresql.org/pg/commitdiff/a3375becfaebde56f8e6260a3f77c467425fbe51">http://git.postgresql.org/pg/commitdiff/a3375becfaebde56f8e6260a3f77c467425fbe51</a>
+</p>
+
+<p>
+- Fix pg_upgrade to print the proper database name for file transfer
+  failures.
+  <a href="http://git.postgresql.org/pg/commitdiff/f7b70dfc7649772cf35035754ae7e77f2533da1d">http://git.postgresql.org/pg/commitdiff/f7b70dfc7649772cf35035754ae7e77f2533da1d</a>
+</p>
+
+<p>
+- Restructure pg_upgrade checks because pre-8.4 Postgres did not
+  rename toast file names to match the new relfilenode.
+  <a href="http://git.postgresql.org/pg/commitdiff/9e5bed2df1693a46dfaed862d7462ba2379f8f79">http://git.postgresql.org/pg/commitdiff/9e5bed2df1693a46dfaed862d7462ba2379f8f79</a>
+</p>
+
+<p>
+- Update new pg_upgrade comment about pre-8.4 TOAST tables.
+  <a href="http://git.postgresql.org/pg/commitdiff/8f87dcd863c2fe2940129ea58343bc0e56cb290c">http://git.postgresql.org/pg/commitdiff/8f87dcd863c2fe2940129ea58343bc0e56cb290c</a>
+</p>
+
+<p>
+- Improve pg_upgrade relation name check logic for pre-8.4 servers.
+  <a href="http://git.postgresql.org/pg/commitdiff/a54ba23c087a23222a7c76b33c61cddad5278712">http://git.postgresql.org/pg/commitdiff/a54ba23c087a23222a7c76b33c61cddad5278712</a>
+</p>
+
+<p>
+- Tighten pg_upgrade check for pre-8.4 toast table name matching.
+  <a href="http://git.postgresql.org/pg/commitdiff/05d93c38a791836eeceaf8edb0ea8cb19cdf2760">http://git.postgresql.org/pg/commitdiff/05d93c38a791836eeceaf8edb0ea8cb19cdf2760</a>
+</p>
+
+<p>
+Simon Riggs pushed:
+</p>
+
+<p>
+- Efficient transaction-controlled synchronous replication.  If a
+  standby is broadcasting reply messages and we have named one or more
+  standbys in synchronous_standby_names then allow users who set
+  synchronous_replication to wait for commit, which then provides
+  strict data integrity guarantees. Design avoids sending and
+  receiving transaction state information so minimises bookkeeping
+  overheads. We synchronize with the highest priority standby that is
+  connected and ready to synchronize. Other standbys can be defined to
+  takeover in case of standby failure.  This version has very strict
+  behaviour; more relaxed options may be added at a later date.  Simon
+  Riggs and Fujii Masao, with reviews by Yeb Havinga, Jaime Casanova,
+  Heikki Linnakangas and Robert Haas, plus the assistance of many
+  other design reviewers.
+  <a href="http://git.postgresql.org/pg/commitdiff/a8a8a3e0965201df88bdfdff08f50e5c06c552b7">http://git.postgresql.org/pg/commitdiff/a8a8a3e0965201df88bdfdff08f50e5c06c552b7</a>
+</p>
+
+<p>
+- Add new files for syncrep missed in previous commit.
+  <a href="http://git.postgresql.org/pg/commitdiff/966fb05b588ab33a6c99c6a26308941e1b3a1188">http://git.postgresql.org/pg/commitdiff/966fb05b588ab33a6c99c6a26308941e1b3a1188</a>
+</p>
+
+<p>
+- Catversion increment for pg_stat_replication changes for syncrep.
+  <a href="http://git.postgresql.org/pg/commitdiff/dcfe3f60c12880c52fd3cb9b5d51ff44c946dd6c">http://git.postgresql.org/pg/commitdiff/dcfe3f60c12880c52fd3cb9b5d51ff44c946dd6c</a>
+</p>
+
+<p>
+- Dynamic array required within pg_stat_replication.
+  <a href="http://git.postgresql.org/pg/commitdiff/cae4974e3d4c0cb1237568b55a2cee4482d42f40">http://git.postgresql.org/pg/commitdiff/cae4974e3d4c0cb1237568b55a2cee4482d42f40</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Fujii Masao sent in another revision of the replication server timeout
+patch.
+</p>
+
+<p>
+Dan Ports sent in a patch to fix a bug in SSI.
+</p>
+
+<p>
+Jan Urbanski sent in a patch to fix PL/PythonU tracebacks.
+</p>
+
+<p>
+Heikki Linnakangas and Merlin Moncure traded patches to fix an issue
+where the PD_ALL_VISIBLE flag was set incorrectly.
+</p>
+
+<p>
+Andy Colson sent in a cleaned-up version of check_rules.pl to conform
+with Perl 5.12.
+</p>
+
+<p>
+Jan Urbanski sent in another revision of the patch to add tracebacks
+to PL/PythonU.
+</p>
+
+<p>
+Fujii Masao sent in another revision of the patch to add replication
+server timeout.
+</p>
+
+<p>
+Kevin Grittner sent in a documentation patch to explain SET
+TRANSACTION...DEFERRABLE better in the context of SSI.
+
+</p>
+
diff --git a/portal/template/en/community/weeklynews/pwn20110313.html b/portal/template/en/community/weeklynews/pwn20110313.html
new file mode 100644
index 00000000..56659ddc
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110313.html
@@ -0,0 +1,786 @@
+<!-- BEGIN page_title_block -->
+Weekly News - March 13 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - March 13 2011</h1>
+
+<p>
+PostgreSQL 9.1alpha4 released, with lots of big, new goodies!
+This is the last planned alpha for 9.1.  You can get it here:
+<a href="http://www.postgresql.org/developer/alpha">http://www.postgresql.org/developer/alpha</a>
+</p>
+
+<p>
+New survey: which 9.1 feature are you most excited about?
+<a href="http://www.postgresql.org/community">http://www.postgresql.org/community</a>
+</p>
+
+<h2>PostgreSQL Jobs for March</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+PostgreSQL Conference East 2011: NYC March 22nd - 25th
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<p>
+There will be a large PostgreSQL presence at the MySQL Conference and
+Expo, April 11-14, 2011 in Santa Clara, California.
+<a href="http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql">http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql</a>
+</p>
+
+<p>
+Open Database Camp will be on May 7-9, 2011 in Sardinia, Italy
+<a href="http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html">http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html</a>
+</p>
+
+<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>
+
+<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>
+Heikki Linnakangas pushed:
+</p>
+
+<p>
+- Silence compiler warning about undefined function when compiling
+  without assertions.
+  <a href="http://git.postgresql.org/pg/commitdiff/baabf05196922164db80bdc45fd0660c8700f1f7">http://git.postgresql.org/pg/commitdiff/baabf05196922164db80bdc45fd0660c8700f1f7</a>
+</p>
+
+<p>
+- Begin error message with lower-case letter.
+  <a href="http://git.postgresql.org/pg/commitdiff/97e3dacd84f185bff86485f54c665621222c576b">http://git.postgresql.org/pg/commitdiff/97e3dacd84f185bff86485f54c665621222c576b</a>
+</p>
+
+<p>
+- Document the DEFERRABLE option in SET TRANSACTION command.  Kevin
+  Grittner
+  <a href="http://git.postgresql.org/pg/commitdiff/faba108fe4f2491ebc2b7faf4343f952125cc661">http://git.postgresql.org/pg/commitdiff/faba108fe4f2491ebc2b7faf4343f952125cc661</a>
+</p>
+
+<p>
+- If recovery_target_timeline is set to 'latest' and standby mode is
+  enabled, periodically rescan the archive for new timelines, while
+  waiting for new WAL segments to arrive. This allows you to set up a
+  standby server that follows the TLI change if another standby server
+  is promoted to master.  Before this, you had to restart the standby
+  server to make it notice the new timeline.  This patch only scans
+  the archive for TLI changes, it won't follow a TLI change in
+  streaming replication. That is much needed too, but it would be a
+  much bigger patch than I dare to sneak in this late in the release
+  cycle.  There was discussion on improving the sanity checking of the
+  WAL segments so that the system would notice more reliably if the
+  new timeline isn't an ancestor of the current one, but that is not
+  included in this patch.  Reviewed by Fujii Masao.
+  <a href="http://git.postgresql.org/pg/commitdiff/1a4ab9ec23f0635a4c15b069df60b545814650e9">http://git.postgresql.org/pg/commitdiff/1a4ab9ec23f0635a4c15b069df60b545814650e9</a>
+</p>
+
+<p>
+- Truncate predicate lock manager's SLRU lazily at checkpoint. That's
+  safer than doing it aggressively whenever the tail-XID pointer is
+  advanced, because this way we don't need to do it while holding
+  SerializableXactHashLock.  This also fixes bug #5915 spotted by
+  YAMAMOTO Takashi, and removes an obsolete comment spotted by Kevin
+  Grittner.
+  <a href="http://git.postgresql.org/pg/commitdiff/4cd3fb6e1244383fc9f77906e7162de0559ba354">http://git.postgresql.org/pg/commitdiff/4cd3fb6e1244383fc9f77906e7162de0559ba354</a>
+</p>
+
+<p>
+- Don't throw a warning if vacuum sees PD_ALL_VISIBLE flag set on a
+  page that contains newly-inserted tuples that according to our
+  OldestXmin are not yet visible to everyone. The value returned by
+  GetOldestXmin() is conservative, and it can move backwards on
+  repeated calls, so if we see that contradiction between the
+  PD_ALL_VISIBLE flag and status of tuples on the page, we have to
+  assume it's because an earlier vacuum calculated a higher OldestXmin
+  value, and all the tuples really are visible to everyone.  We have
+  received several reports of this bug, with the "PD_ALL_VISIBLE flag
+  was incorrectly set in relation ..." warning appearing in logs. We
+  were finally able to hunt it down with David Gould's help to run
+  extra diagnostics in an environment where this happened frequently.
+  Also reword the warning, per Robert Haas' suggestion, to not imply
+  that the PD_ALL_VISIBLE flag is necessarily at fault, as it might
+  also be a symptom of corruption on a tuple header.  Backpatch to
+  8.4, where the PD_ALL_VISIBLE flag was introduced.
+  <a href="http://git.postgresql.org/pg/commitdiff/93d888232e80e4d676e24fe93ae6d27459d966be">http://git.postgresql.org/pg/commitdiff/93d888232e80e4d676e24fe93ae6d27459d966be</a>
+</p>
+
+<p>
+- Fix overly strict assertion in SummarizeOldestCommittedSxact().
+  There's a race condition where SummarizeOldestCommittedSxact() is
+  called even though another backend already cleared out all finished
+  sxact entries.  That's OK, RegisterSerializableTransactionInt() can
+  just retry getting a news xact slot from the available-list when
+  that happens.  Reported by YAMAMOTO Takashi, bug #5918.
+  <a href="http://git.postgresql.org/pg/commitdiff/46c333a9638b329a3c8076d978f27c5b05c0d5f0">http://git.postgresql.org/pg/commitdiff/46c333a9638b329a3c8076d978f27c5b05c0d5f0</a>
+</p>
+
+<p>
+- Fix bugs in the isolation tester flex rules.  Tom Lane pointed out
+  that it was giving a warning: "-s option given but default rule can
+  be matched". That was because there was no rule to handle newline in
+  a quoted string. I made that throw an error.  Also, line number
+  tracking was broken, giving incorrect line number on error. Fixed
+  that too.
+  <a href="http://git.postgresql.org/pg/commitdiff/74a09d92101f36a5fe66f4f74253708931546e4c">http://git.postgresql.org/pg/commitdiff/74a09d92101f36a5fe66f4f74253708931546e4c</a>
+</p>
+
+<p>
+- In ecpg preprocessor, don't try to look up constants in the test for
+  variable hiding. A constant is not a variable. It worked in most
+  cases by accident, because we add constants to the global list of
+  variables (why?), but float constants like 1.23 were interpreted as
+  struct field references, and not found.  Backpatch to 9.0, where the
+  test for variable hiding was added.
+  <a href="http://git.postgresql.org/pg/commitdiff/30e8b3e58ed56cbc07ae7cd392ee4b9782178ca5">http://git.postgresql.org/pg/commitdiff/30e8b3e58ed56cbc07ae7cd392ee4b9782178ca5</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Zero out vacuum_count and related counters in pgstat_recv_tabstat().
+  This fixes an oversight in commit 946045f04d11d246a834b917a2b8bc6e4f884a37
+  of 2010-08-21, as reported by Itagaki Takahiro.  Also a couple of
+  minor cosmetic adjustments.
+  <a href="http://git.postgresql.org/pg/commitdiff/7193a90fc1e3ce0be7688c1452e813bd0ddc101b">http://git.postgresql.org/pg/commitdiff/7193a90fc1e3ce0be7688c1452e813bd0ddc101b</a>
+</p>
+
+<p>
+- Minor copy-editing in CREATE TRIGGER reference page.  Per
+  suggestions from Thom Brown and Robert Haas.
+  <a href="http://git.postgresql.org/pg/commitdiff/f8c0af840d84086249647d4415bd35903bfc7933">http://git.postgresql.org/pg/commitdiff/f8c0af840d84086249647d4415bd35903bfc7933</a>
+</p>
+
+<p>
+- Improve description of inquiry functions that accept regclass.  Per
+  a suggestion from Thom Brown, though this is not his proposed patch.
+  <a href="http://git.postgresql.org/pg/commitdiff/cfcdc99db67172d46a5e226375fa97e5c5a62267">http://git.postgresql.org/pg/commitdiff/cfcdc99db67172d46a5e226375fa97e5c5a62267</a>
+</p>
+
+<p>
+- Add missing keywords to gram.y's unreserved_keywords list.  We
+  really need an automated check for this ... and did VALIDATE really
+  need to become a keyword at all, rather than picking some other
+  syntax using existing keywords?
+  <a href="http://git.postgresql.org/pg/commitdiff/3f7d24da16d32ad0fa5abf04b669e86a7d458160">http://git.postgresql.org/pg/commitdiff/3f7d24da16d32ad0fa5abf04b669e86a7d458160</a>
+</p>
+
+<p>
+- Assorted editing for collation documentation.  I made a pass over
+  this to familiarize myself with the feature, and found some things
+  that could be improved.
+  <a href="http://git.postgresql.org/pg/commitdiff/a612b17120fc011cefcdec6948b1cc8543529d06">http://git.postgresql.org/pg/commitdiff/a612b17120fc011cefcdec6948b1cc8543529d06</a>
+</p>
+
+<p>
+- A bit more editing for collation documentation.
+  <a href="http://git.postgresql.org/pg/commitdiff/c0dc44ebba0bbce430e71adb195ceec66417d40b">http://git.postgresql.org/pg/commitdiff/c0dc44ebba0bbce430e71adb195ceec66417d40b</a>
+</p>
+
+<p>
+- Adjust the permissions required for COMMENT ON ROLE.  Formerly, any
+  member of a role could change the role's comment, as of course could
+  superusers; but holders of CREATEROLE privilege could not, unless
+  they were also members.  This led to the odd situation that a
+  CREATEROLE holder could create a role but then could not comment on
+  it.  It also seems a bit dubious to let an unprivileged user change
+  his own comment, let alone those of group roles he belongs to.  So,
+  change the rule to be "you must be superuser to comment on a
+  superuser role, or hold CREATEROLE to comment on non-superuser
+  roles".  This is the same as the privilege check for
+  creating/dropping roles, and thus fits much better with the rule for
+  other object types, namely that only the owner of an object can
+  comment on it.  In passing, clean up the documentation for COMMENT a
+  little bit.  Per complaint from Owen Jacobson and subsequent
+  discussion.
+  <a href="http://git.postgresql.org/pg/commitdiff/49a08ca1e968860fe02fa3331cc0aba361d76e02">http://git.postgresql.org/pg/commitdiff/49a08ca1e968860fe02fa3331cc0aba361d76e02</a>
+</p>
+
+<p>
+- Remove collation information from TypeName, where it does not
+  belong.  The initial collations patch treated a COLLATE spec as part
+  of a TypeName, following what can only be described as brain fade on
+  the part of the SQL committee.  It's a lot more reasonable to treat
+  COLLATE as a syntactically separate object, so that it can be added
+  in only the productions where it actually belongs, rather than
+  needing to reject it in a boatload of places where it doesn't belong
+  (something the original patch mostly failed to do).  In addition
+  this change lets us meet the spec's requirement to allow COLLATE
+  anywhere in the clauses of a ColumnDef, and it avoids unfriendly
+  behavior for constructs such as "foo::type COLLATE collation".  To
+  do this, pull collation information out of TypeName and put it in
+  ColumnDef instead, thus reverting most of the collation-related
+  changes in parse_type.c's API.  I made one additional structural
+  change, which was to use a ColumnDef as an intermediate node in
+  AT_AlterColumnType AlterTableCmd nodes.  This provides enough room
+  to get rid of the "transform" wart in AlterTableCmd too, since the
+  ColumnDef can carry the USING expression easily enough.  Also fix
+  some other minor bugs that have crept in in the same areas, like
+  failure to copy recently-added fields of ColumnDef in copyfuncs.c.
+  While at it, document the formerly secret ability to specify a
+  collation in ALTER TABLE ALTER COLUMN TYPE, ALTER TYPE ADD
+  ATTRIBUTE, and ALTER TYPE ALTER ATTRIBUTE TYPE; and correct some
+  misstatements about what the default collation selection will be
+  when COLLATE is omitted.  BTW, the three-parameter form of
+  format_type() should go away too, since it just contributes to the
+  confusion in this area; but I'll do that in a separate patch.
+  <a href="http://git.postgresql.org/pg/commitdiff/a051ef699c3ed1f89088dd6bbc2574f13d0b20eb">http://git.postgresql.org/pg/commitdiff/a051ef699c3ed1f89088dd6bbc2574f13d0b20eb</a>
+</p>
+
+<p>
+- Fix some oversights in distprep and maintainer-clean targets.  At
+  least two recent commits have apparently imagined that a comment in
+  a Makefile stating that something would be included in the
+  distribution tarball was sufficient to make it so.  They hadn't
+  bothered to hook into the upper maintainer-clean targets either.
+  Per bug #5923 from Charles Johnson, in which it emerged that the
+  9.1alpha4 tarballs are short a few files that should be there.
+  <a href="http://git.postgresql.org/pg/commitdiff/174f65ab00bb8de0f119a6a60d562b516ba71bba">http://git.postgresql.org/pg/commitdiff/174f65ab00bb8de0f119a6a60d562b516ba71bba</a>
+</p>
+
+<p>
+- replication/repl_gram.h needs to be cleaned too ...
+  <a href="http://git.postgresql.org/pg/commitdiff/f6587019ed2c2123c00c18db2d1e857a6258ff85">http://git.postgresql.org/pg/commitdiff/f6587019ed2c2123c00c18db2d1e857a6258ff85</a>
+</p>
+
+<p>
+- Revert addition of third argument to format_type().  Including
+  collation in the behavior of that function promotes a world view we
+  do not want.  Moreover, it was producing the wrong behavior for
+  pg_dump anyway: what we want is to dump a COLLATE clause on
+  attributes whose attcollation is different from the underlying type,
+  and likewise for domains, and the function cannot do that for us.
+  Doing it the hard way in pg_dump is a bit more tedious but produces
+  more correct output.  In passing, fix initdb so that the initial
+  entry in pg_collation is properly pinned.  It was droppable before
+  :-(
+  <a href="http://git.postgresql.org/pg/commitdiff/7564654adf07ec26b83c7effc7f54f7183e04519">http://git.postgresql.org/pg/commitdiff/7564654adf07ec26b83c7effc7f54f7183e04519</a>
+</p>
+
+<p>
+- Remove duplicate indexterm to silence openjade wrning.
+  <a href="http://git.postgresql.org/pg/commitdiff/ac435a79c88f51be6bf3eb5df618c2bac6123ae4">http://git.postgresql.org/pg/commitdiff/ac435a79c88f51be6bf3eb5df618c2bac6123ae4</a>
+</p>
+
+<p>
+- Create an explicit concept of collations that work for any encoding.
+  Use collencoding = -1 to represent such a collation in pg_collation.
+  We need this to make the "default" entry work sanely, and a later
+  patch will fix the C/POSIX entries to be represented this way
+  instead of duplicating them across all encodings.  All lookup
+  operations now search first for an entry that's
+  database-encoding-specific, and then for the same name with
+  collencoding = -1.  Also some incidental code cleanup in
+  collationcmds.c and pg_collation.c.
+  <a href="http://git.postgresql.org/pg/commitdiff/e3c732a85c0f247617b2d44ea567f35731b03ea6">http://git.postgresql.org/pg/commitdiff/e3c732a85c0f247617b2d44ea567f35731b03ea6</a>
+</p>
+
+<p>
+- Split CollateClause into separate raw and analyzed node types.
+  CollateClause is now used only in raw grammar output, and
+  CollateExpr after parse analysis.  This is for clarity and to avoid
+  carrying collation names in post-analysis parse trees: that's both
+  wasteful and possibly misleading, since the collation's name could
+  be changed while the parsetree still exists.  Also, clean up
+  assorted infelicities and omissions in processing of the node type.
+  <a href="http://git.postgresql.org/pg/commitdiff/8acdb8bf9cebc42cee5aa96a2d594756b44173c9">http://git.postgresql.org/pg/commitdiff/8acdb8bf9cebc42cee5aa96a2d594756b44173c9</a>
+</p>
+
+<p>
+- Put in some more safeguards against executing a division-by-zero.
+  Add dummy returns before every potential division-by-zero in int8.c,
+  because apparently further "improvements" in gcc's optimizer have
+  enabled it to break functions that weren't broken before.  Aurelien
+  Jarno, via Martin Pitt
+  <a href="http://git.postgresql.org/pg/commitdiff/72330995a52fb7a3fbdc666aebc0402cdcbc9af8">http://git.postgresql.org/pg/commitdiff/72330995a52fb7a3fbdc666aebc0402cdcbc9af8</a>
+</p>
+
+<p>
+- On further reflection, we'd better do the same in int.c.  We
+  previously heard of the same problem in int24div(), so there's not a
+  good reason to suppose the problem is confined to cases involving
+  int8.
+  <a href="http://git.postgresql.org/pg/commitdiff/2a26639a5d76df7f59340cfb4313763f87815ede">http://git.postgresql.org/pg/commitdiff/2a26639a5d76df7f59340cfb4313763f87815ede</a>
+</p>
+
+<p>
+- Make all comparisons done for/with statistics use the default
+  collation.  While this will give wrong answers when estimating
+  selectivity for a comparison operator that's using a non-default
+  collation, the estimation error probably won't be large; and anyway
+  the former approach created estimation errors of its own by trying
+  to use a histogram that might have been computed with some other
+  collation.  So we'll adopt this simplified approach for now and
+  perhaps improve it sometime in the future.  This patch incorporates
+  changes from Andres Freund to make sure that selfuncs.c passes a
+  valid collation OID to any datatype-specific function it calls, in
+  case that function wants collation information.  Said OID will now
+  always be DEFAULT_COLLATION_OID, but at least we won't get errors.
+  <a href="http://git.postgresql.org/pg/commitdiff/696d1f7f064402840a60b7177a838d1452ad13e6">http://git.postgresql.org/pg/commitdiff/696d1f7f064402840a60b7177a838d1452ad13e6</a>
+</p>
+
+<p>
+- Simplify list traversal logic in add_path().  Its mechanism for
+  recovering after deleting the current list cell was a bit klugy.
+  Borrow the technique used in other places.
+  <a href="http://git.postgresql.org/pg/commitdiff/a2eb9e0c08ee73208b5419f5a53a6eba55809b92">http://git.postgresql.org/pg/commitdiff/a2eb9e0c08ee73208b5419f5a53a6eba55809b92</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Synchronous replication doc corrections.  Thom Brown
+  <a href="http://git.postgresql.org/pg/commitdiff/c74d3aceb99ea6c6d102109349b514e76e497592">http://git.postgresql.org/pg/commitdiff/c74d3aceb99ea6c6d102109349b514e76e497592</a>
+</p>
+
+<p>
+- Reword alpha release note item on SSI.  Per Josh Berkus; some
+  additional explanatory text by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/bcf85e3f44a518eb7bb759541189efb6726fe9bc">http://git.postgresql.org/pg/commitdiff/bcf85e3f44a518eb7bb759541189efb6726fe9bc</a>
+</p>
+
+<p>
+- Create "replication and recovery" section in alpha release notes.
+  <a href="http://git.postgresql.org/pg/commitdiff/51c0124481213eab45db193929614070da7b60d1">http://git.postgresql.org/pg/commitdiff/51c0124481213eab45db193929614070da7b60d1</a>
+</p>
+
+<p>
+- Update alpha release notes for latest commits.
+  <a href="http://git.postgresql.org/pg/commitdiff/f14ae5f905282109c9a2571c2048c564004f24c5">http://git.postgresql.org/pg/commitdiff/f14ae5f905282109c9a2571c2048c564004f24c5</a>
+</p>
+
+<p>
+- Make alpha release notes more consistent as regards periods.
+  <a href="http://git.postgresql.org/pg/commitdiff/26ed3fdb4553a0e52c8534292de0f39bfc2c5022">http://git.postgresql.org/pg/commitdiff/26ed3fdb4553a0e52c8534292de0f39bfc2c5022</a>
+</p>
+
+<p>
+- Replication README updates.  Fujii Masao
+  <a href="http://git.postgresql.org/pg/commitdiff/fcb99609b60012bc2e828b8941d5db46f2625f4a">http://git.postgresql.org/pg/commitdiff/fcb99609b60012bc2e828b8941d5db46f2625f4a</a>
+</p>
+
+<p>
+- Add missing index terms for recovery control functions.  Fujii Masao
+  <a href="http://git.postgresql.org/pg/commitdiff/1c3b434a0897a727127b7c4083f2bfa2c9b690c3">http://git.postgresql.org/pg/commitdiff/1c3b434a0897a727127b7c4083f2bfa2c9b690c3</a>
+</p>
+
+<p>
+- Emit a LOG message when pausing at the recovery target.  Fujii Masao
+  <a href="http://git.postgresql.org/pg/commitdiff/d16e290a8a52d76d01ef1d70f8c33336942a0870">http://git.postgresql.org/pg/commitdiff/d16e290a8a52d76d01ef1d70f8c33336942a0870</a>
+</p>
+
+<p>
+- Minor sync rep corrections.  Fujii Masao, with a bit of additional
+  wordsmithing by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/64360987953e450e53098e6b79d89c5b80dc7842">http://git.postgresql.org/pg/commitdiff/64360987953e450e53098e6b79d89c5b80dc7842</a>
+</p>
+
+<p>
+- Remove obsolete comment.  In earlier versions of the sync rep patch,
+  waiters removed themselves from the queue, but now walsender removes
+  them before doing the wakeup.  Report by Fujii Masao.
+  <a href="http://git.postgresql.org/pg/commitdiff/e397d2ee6474865becb8f99ac28586736788f1f2">http://git.postgresql.org/pg/commitdiff/e397d2ee6474865becb8f99ac28586736788f1f2</a>
+</p>
+
+<p>
+- More synchronous replication tweaks.  SyncRepRequested() must check
+  not only the value of the synchronous_replication GUC but also
+  whether max_wal_senders > 0.  Otherwise, we might end up waiting for
+  sync rep even when there's no possibility of a standby ever managing
+  to connect.  There are some existing cross-checks to prevent this,
+  but they're not quite sufficient: the user can start the server with
+  max_wal_senders=0, synchronous_standby_names='', and
+  synchronous_replication=off and then subsequent make
+  synchronous_standby_names not empty using pg_ctl reload, and then
+  SET synchronous_standby=on, leading to an indefinite hang.  Along
+  the way, rename the global variable for the synchronous_replication
+  GUC to match the name of the GUC itself, for clarity.  Report by
+  Fujii Masao, though I didn't use his patch.
+  <a href="http://git.postgresql.org/pg/commitdiff/b8bb8dbf20e13087f8e57ff4c42e81776ae5e545">http://git.postgresql.org/pg/commitdiff/b8bb8dbf20e13087f8e57ff4c42e81776ae5e545</a>
+</p>
+
+<p>
+- More synchronous replication typo fixes.  Fujii Masao
+  <a href="http://git.postgresql.org/pg/commitdiff/2e019c8611654175780db488d81cc2dc8311f22e">http://git.postgresql.org/pg/commitdiff/2e019c8611654175780db488d81cc2dc8311f22e</a>
+</p>
+
+<p>
+- Make error handling of synchronous_standby_names consistent.  It's
+  not a good idea to kill the postmaster just because someone muffs
+  this, and it's not consistent with what we do for other, similar
+  GUCs.  Fujii Masao, with a bit more hacking by me
+  <a href="http://git.postgresql.org/pg/commitdiff/551c07d84ae2f0d3b7dde68e52322edf9cb87ba5">http://git.postgresql.org/pg/commitdiff/551c07d84ae2f0d3b7dde68e52322edf9cb87ba5</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Fix behavior when raising plpy.Fatal().  It should cause a
+  elog(FATAL) error, and it fact it was simply causing a elog(ERROR).
+  Jan Urbański
+  <a href="http://git.postgresql.org/pg/commitdiff/804d13adfd2f66c70d8d95a606dde621b3213179">http://git.postgresql.org/pg/commitdiff/804d13adfd2f66c70d8d95a606dde621b3213179</a>
+</p>
+
+<p>
+- Report Python errors from iterators with PLy_elog.  This improves
+  reporting, as the error string now includes the actual Python
+  exception. As a side effect, this no longer sets the errcode to
+  ERRCODE_DATA_EXCEPTION, which might be considered a feature, as it's
+  not documented and not clear why iterator errors should be treated
+  differently.  Jan Urbański.
+  <a href="http://git.postgresql.org/pg/commitdiff/8f76324352986287c04832f8e6450d4d2952a030">http://git.postgresql.org/pg/commitdiff/8f76324352986287c04832f8e6450d4d2952a030</a>
+</p>
+
+<p>
+- Ignore files built by coverage builds.
+  <a href="http://git.postgresql.org/pg/commitdiff/a2f216547740819bdd79e05039c525350d7c3d0f">http://git.postgresql.org/pg/commitdiff/a2f216547740819bdd79e05039c525350d7c3d0f</a>
+</p>
+
+<p>
+- Fix parallel make when running make install before make all.  In
+  addition to the all-foo-recurse: all-bar-recurse dependencies that
+  constraint the order of the rule execution, we need
+  install-foo-recurse: install-bar-recurse dependencies in case one
+  runs make install without a make all first, as some people
+  apparently do.
+  <a href="http://git.postgresql.org/pg/commitdiff/4502c8e1c06164adb7be526096e91e04d1844d36">http://git.postgresql.org/pg/commitdiff/4502c8e1c06164adb7be526096e91e04d1844d36</a>
+</p>
+
+<p>
+- Add test case for collation mismatch in recursive query.  This isn't
+  very important by itself, but was left on my list of things without
+  test coverage for the collation feature.
+  <a href="http://git.postgresql.org/pg/commitdiff/3d9f7ec1ffde399accda096da4df46b178e8b960">http://git.postgresql.org/pg/commitdiff/3d9f7ec1ffde399accda096da4df46b178e8b960</a>
+</p>
+
+<p>
+Michael Meskes pushed:
+</p>
+
+<p>
+- Added new version of ecpg's parser test script which was written by
+  Andy Colson.
+  <a href="http://git.postgresql.org/pg/commitdiff/4ff90d9945b2e33662b2a0af2cad69ae802f2b76">http://git.postgresql.org/pg/commitdiff/4ff90d9945b2e33662b2a0af2cad69ae802f2b76</a>
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Document that char() ignores spaces in non-pattern comparisons, not
+  in pattern comparisons such as LIKE and regex.
+  <a href="http://git.postgresql.org/pg/commitdiff/7465ae06be4f1dbc90575d68d1ffc3351e1ca855">http://git.postgresql.org/pg/commitdiff/7465ae06be4f1dbc90575d68d1ffc3351e1ca855</a>
+</p>
+
+<p>
+- Adjust CHAR() doc mention of pattern matching issues for trailing
+  spaces.
+  <a href="http://git.postgresql.org/pg/commitdiff/915cd10c164be27dac0134efb16358f7d7564e8d">http://git.postgresql.org/pg/commitdiff/915cd10c164be27dac0134efb16358f7d7564e8d</a>
+</p>
+
+<p>
+- Fix file descriptor leaks in pg_upgrade in failure code paths.
+  <a href="http://git.postgresql.org/pg/commitdiff/d367d41d662c859011724745fec592baf94b70fe">http://git.postgresql.org/pg/commitdiff/d367d41d662c859011724745fec592baf94b70fe</a>
+</p>
+
+<p>
+- Improve wording of initdb and pg_controldata manual pages.
+  Gabrielle Roth.
+  <a href="http://git.postgresql.org/pg/commitdiff/8cc55b1c0fbf9a2e01d14311716b59d19314126e">http://git.postgresql.org/pg/commitdiff/8cc55b1c0fbf9a2e01d14311716b59d19314126e</a>
+</p>
+
+<p>
+- Remove '=' from initdb switch syntax.
+  <a href="http://git.postgresql.org/pg/commitdiff/c290476cbd2e2d5f8f6c7c24ebaa5133ec37ecde">http://git.postgresql.org/pg/commitdiff/c290476cbd2e2d5f8f6c7c24ebaa5133ec37ecde</a>
+</p>
+
+<p>
+- Document that server single-user mode does not do checkpoints or
+  other background processing.
+  <a href="http://git.postgresql.org/pg/commitdiff/01752f7bba627c0c38d594b27e50238015272828">http://git.postgresql.org/pg/commitdiff/01752f7bba627c0c38d594b27e50238015272828</a>
+</p>
+
+<p>
+- Mention gcc version in C comment.
+  <a href="http://git.postgresql.org/pg/commitdiff/76fdee31c4ff74b7eae5965521a85d29381bcaec">http://git.postgresql.org/pg/commitdiff/76fdee31c4ff74b7eae5965521a85d29381bcaec</a>
+</p>
+
+<p>
+- Use '=' when documenting long options.
+  <a href="http://git.postgresql.org/pg/commitdiff/ed0327495c4241fad55a61c0e5d54366c3ea076c">http://git.postgresql.org/pg/commitdiff/ed0327495c4241fad55a61c0e5d54366c3ea076c</a>
+</p>
+
+<p>
+- Add proper git-external-diff script to src/tools.
+  <a href="http://git.postgresql.org/pg/commitdiff/9d4625ad0b836538618e324b4ebbc3ba366447a1">http://git.postgresql.org/pg/commitdiff/9d4625ad0b836538618e324b4ebbc3ba366447a1</a>
+</p>
+
+<p>
+- Clarify what commands are not allowed in SQL functions.
+  <a href="http://git.postgresql.org/pg/commitdiff/678a0d286c2928aa85bcf25e5c3c633e88e44999">http://git.postgresql.org/pg/commitdiff/678a0d286c2928aa85bcf25e5c3c633e88e44999</a>
+</p>
+
+<p>
+- Improve SQL function disallowed command wording.
+  <a href="http://git.postgresql.org/pg/commitdiff/2fdd357cae8ac4dc472375301bde701b2bf76f54">http://git.postgresql.org/pg/commitdiff/2fdd357cae8ac4dc472375301bde701b2bf76f54</a>
+</p>
+
+<p>
+- More wording improvements for disallowed SQL function commands.
+  <a href="http://git.postgresql.org/pg/commitdiff/3aa6041db5706821295da34b47c60b18a0a34021">http://git.postgresql.org/pg/commitdiff/3aa6041db5706821295da34b47c60b18a0a34021</a>
+</p>
+
+<p>
+- Reference doc "examples" section for pg_dump options that often need
+  complex quoting, e.g. -t and -n.
+  <a href="http://git.postgresql.org/pg/commitdiff/26174d5fd0dec01bbbc4e766ed32b9a50a019c29">http://git.postgresql.org/pg/commitdiff/26174d5fd0dec01bbbc4e766ed32b9a50a019c29</a>
+</p>
+
+<p>
+- Clarify C comment that O_SYNC/O_FSYNC are really the same settting,
+  as opposed to O_DSYNC.
+  <a href="http://git.postgresql.org/pg/commitdiff/5ca543fb2e2ca5becdb6505ac22aaf7218e842cf">http://git.postgresql.org/pg/commitdiff/5ca543fb2e2ca5becdb6505ac22aaf7218e842cf</a>
+</p>
+
+<p>
+- Modify pg_test_fsync to match the behavior of git head in regards to
+  O_DIRECT behavior.
+  <a href="http://git.postgresql.org/pg/commitdiff/303b7fcd10a34d8c8b4c3e6e258faeaf107dcf92">http://git.postgresql.org/pg/commitdiff/303b7fcd10a34d8c8b4c3e6e258faeaf107dcf92</a>
+</p>
+
+<p>
+- When a smart pg_ctl shutdown fails, mention -m fast as a tip.
+  <a href="http://git.postgresql.org/pg/commitdiff/3f9cf6b336fb93f4e13943d9e873f5a4a167177a">http://git.postgresql.org/pg/commitdiff/3f9cf6b336fb93f4e13943d9e873f5a4a167177a</a>
+</p>
+
+<p>
+- Add C comment that new new pg_dump -X options are to be created.
+  <a href="http://git.postgresql.org/pg/commitdiff/c3462e413e8700b4710a6d23252fd095291c27e3">http://git.postgresql.org/pg/commitdiff/c3462e413e8700b4710a6d23252fd095291c27e3</a>
+</p>
+
+<p>
+- Remove pg_dump -X options that are only in 9.1 and not needed for
+  backward compatibility.
+  <a href="http://git.postgresql.org/pg/commitdiff/72bd19dbddaf5786381377ad3da281572de721b5">http://git.postgresql.org/pg/commitdiff/72bd19dbddaf5786381377ad3da281572de721b5</a>
+</p>
+
+<p>
+- Change "TIP" to "HINT" to match backend message style, in pg_ctl -m
+  fast suggestion.
+  <a href="http://git.postgresql.org/pg/commitdiff/f887294ccfad1545f8c94e7d486ffdd90a61132e">http://git.postgresql.org/pg/commitdiff/f887294ccfad1545f8c94e7d486ffdd90a61132e</a>
+</p>
+
+<p>
+- Add comment to tools/git-external-diff.
+  <a href="http://git.postgresql.org/pg/commitdiff/dae1e5546cdff98d85215a461f108f71fd254441">http://git.postgresql.org/pg/commitdiff/dae1e5546cdff98d85215a461f108f71fd254441</a>
+</p>
+
+<p>
+- Document that the parenthesized VACUUM syntax is deprecated, not the
+  FREEZE functionality.
+  <a href="http://git.postgresql.org/pg/commitdiff/ad44d505917baf35994f3eabdb42657bf2342b99">http://git.postgresql.org/pg/commitdiff/ad44d505917baf35994f3eabdb42657bf2342b99</a>
+</p>
+
+<p>
+- Document that libpq's PQgetResult() should be called after a fatal
+  error to fully process errors.
+  <a href="http://git.postgresql.org/pg/commitdiff/06711de9d9d4e122d4e4c9b801b471e048281f48">http://git.postgresql.org/pg/commitdiff/06711de9d9d4e122d4e4c9b801b471e048281f48</a>
+</p>
+
+<p>
+- Update C comment about O_DIRECT and fsync().
+  <a href="http://git.postgresql.org/pg/commitdiff/7d23e0f803fc0af0ff7b317a504eba31a51ebade">http://git.postgresql.org/pg/commitdiff/7d23e0f803fc0af0ff7b317a504eba31a51ebade</a>
+</p>
+
+<p>
+- Document that pg_dump --clean might generate some harmless errors on
+  restore.
+  <a href="http://git.postgresql.org/pg/commitdiff/afaed3add89ffe3df422319c3a76761e186efe30">http://git.postgresql.org/pg/commitdiff/afaed3add89ffe3df422319c3a76761e186efe30</a>
+</p>
+
+<p>
+- Update kernel docs for Solaris 10.  Josh Berkus
+  <a href="http://git.postgresql.org/pg/commitdiff/3896138b7c18c89f57d35fcb85a369d89323e827">http://git.postgresql.org/pg/commitdiff/3896138b7c18c89f57d35fcb85a369d89323e827</a>
+</p>
+
+<p>
+- Fix "unparenthesized" mention in vacuum docs.
+  <a href="http://git.postgresql.org/pg/commitdiff/ea5c4c71f610712a0d492fd39a0d9db102b6054f">http://git.postgresql.org/pg/commitdiff/ea5c4c71f610712a0d492fd39a0d9db102b6054f</a>
+</p>
+
+<p>
+- Improve extract(day) documentation with interval values.
+  <a href="http://git.postgresql.org/pg/commitdiff/cbd2811461daf2c6b71d56048b96374cc2d61d64">http://git.postgresql.org/pg/commitdiff/cbd2811461daf2c6b71d56048b96374cc2d61d64</a>
+</p>
+
+<p>
+- In plpsql docs, use RAISE rather than undefined log function.
+  <a href="http://git.postgresql.org/pg/commitdiff/35a1964e557ad5993a94e8b800135f55b6347926">http://git.postgresql.org/pg/commitdiff/35a1964e557ad5993a94e8b800135f55b6347926</a>
+</p>
+
+<p>
+- Adds index entries for session_user and pg_describe_object. Removes
+  extraneous closing parenthesis from pg_describe_object. Puts
+  pg_describe_object and has_sequence_privilege in correct
+  alphabetical position in function listing.  Thom Brown
+  <a href="http://git.postgresql.org/pg/commitdiff/59bacbe1470b7b3c4382284301267b18daf98e93">http://git.postgresql.org/pg/commitdiff/59bacbe1470b7b3c4382284301267b18daf98e93</a>
+</p>
+
+<p>
+- Document how listen_addresses can do only IPv4 or IPv6.
+  <a href="http://git.postgresql.org/pg/commitdiff/a1bb5a480df44e518957abca0de2d04aaba5bf02">http://git.postgresql.org/pg/commitdiff/a1bb5a480df44e518957abca0de2d04aaba5bf02</a>
+</p>
+
+<p>
+- Document that to_char('FM') removes only trailing zeros.
+  <a href="http://git.postgresql.org/pg/commitdiff/ffe92d15d53625d5ae0c23f4e1984ed43614a33d">http://git.postgresql.org/pg/commitdiff/ffe92d15d53625d5ae0c23f4e1984ed43614a33d</a>
+</p>
+
+<p>
+- Update documentation on FreeBSD write cache control.
+  <a href="http://git.postgresql.org/pg/commitdiff/4869d10afc74e9cc774942c24b48cef301a0a693">http://git.postgresql.org/pg/commitdiff/4869d10afc74e9cc774942c24b48cef301a0a693</a>
+</p>
+
+<p>
+- In docs, rename "backwards compatibility" to "backward
+  compatibility" for consistency.
+  <a href="http://git.postgresql.org/pg/commitdiff/7a8f43968add3c69b79c49ef236d945e643dcb1e">http://git.postgresql.org/pg/commitdiff/7a8f43968add3c69b79c49ef236d945e643dcb1e</a>
+</p>
+
+<p>
+- Use macros for time-based constants, rather than constants.
+  <a href="http://git.postgresql.org/pg/commitdiff/3a3f39fdc00c6caa41d795475189ac844403b770">http://git.postgresql.org/pg/commitdiff/3a3f39fdc00c6caa41d795475189ac844403b770</a>
+</p>
+
+<p>
+- Use "backend process" rather than "backend server", where
+  appropriate.
+  <a href="http://git.postgresql.org/pg/commitdiff/94fe9c0f4e1672ccd830cb0aa7fd5ccce97d14ae">http://git.postgresql.org/pg/commitdiff/94fe9c0f4e1672ccd830cb0aa7fd5ccce97d14ae</a>
+</p>
+
+<p>
+ITAGAKI Takahiro pushed:
+</p>
+
+<p>
+- synchronous_standby_names is a string parameter.
+  <a href="http://git.postgresql.org/pg/commitdiff/1144726d070746a857a13af271e2864961a5268f">http://git.postgresql.org/pg/commitdiff/1144726d070746a857a13af271e2864961a5268f</a>
+</p>
+
+<p>
+- Remove 's' from recovery_target_timeline's' from the release note.
+  <a href="http://git.postgresql.org/pg/commitdiff/48ff3913d6ce42cd090d17ea6863be4698007afe">http://git.postgresql.org/pg/commitdiff/48ff3913d6ce42cd090d17ea6863be4698007afe</a>
+</p>
+
+<p>
+- Cleanup copyright years and file names in the header comments of
+  some files.
+  <a href="http://git.postgresql.org/pg/commitdiff/2d8de0a50b54cc0ed430ffa96dc8776dfe95d5ff">http://git.postgresql.org/pg/commitdiff/2d8de0a50b54cc0ed430ffa96dc8776dfe95d5ff</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Jan Urbanski sent in another flock of patches to fix PL/PythonU.
+</p>
+
+<p>
+Fujii Masao sent in another revision of the replication server timeout
+patch.
+</p>
+
+<p>
+Thom Brown sent in two revisions of doc patches for syncrep.
+</p>
+
+<p>
+Fujii Masao sent in four revisions of a patch to add a sample
+recovery.conf which illustrates the use of recovery control functions.
+</p>
+
+<p>
+Gurjeet Singh sent in another revision of the patch to allow psql to
+use relative paths for includes, this time with a long option
+(\include_relative).
+</p>
+
+<p>
+Noah Misch sent in a patch to add test for FOR KEY LOCK.
+</p>
+
+<p>
+Mark Kirkwood sent in another revision of the patch to constrain
+backend temporary file space.
+</p>
+
+<p>
+Kevin Grittner sent in a patch to reformat the SSI files per pgindent.
+</p>
+
+<p>
+Bruce Momjian and Christopher Browne traded patches to make constants
+for magic time values.
+</p>
+
+<p>
+Robert Haas sent in a patch to enable ALTER TABLE ... ALTER CONSTRAINT
+... VALID, which makes the system check whether the constraint is true
+if not already enforced.
+</p>
+
+<p>
+Noah Misch sent in a patch to fix an issue with on-the-fly index tuple
+deletion and hot standby.
+</p>
+
+<p>
+Bruce Momjian sent in a patch to add a comment to the template0
+database.
+</p>
+
+<p>
+Robert Haas sent in a patch to add the new keywords 9.1 features have
+spawned.
+</p>
+
+<p>
+Noah Misch sent in a patch to fix some memory-related bugs he turned
+up while testing an instrumented version of PostgreSQL.
+
+</p>
+
diff --git a/portal/template/en/community/weeklynews/pwn20110320.html b/portal/template/en/community/weeklynews/pwn20110320.html
new file mode 100644
index 00000000..4d135f2a
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110320.html
@@ -0,0 +1,534 @@
+<!-- BEGIN page_title_block -->
+Weekly News - March 20 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - March 20 2011</h1>
+
+<p>
+PostgreSQL was accepted as a mentoring organization for Google Summer
+of Code 2011!  If you are a student interested in applying,
+applications open March 28, 2011.  Details and ideas for projects here:
+<a href="http://wiki.postgresql.org/wiki/GSoC_2011">http://wiki.postgresql.org/wiki/GSoC_2011</a>
+</p>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+bucardo 4.4.2, a PostgreSQL replication system, released:
+<a href="http://bucardo.org/wiki/Bucardo">http://bucardo.org/wiki/Bucardo</a>
+</p>
+
+<p>
+tail_n_mail 1.17.6, a log file alerting tool, released:
+<a href="http://bucardo.org/wiki/Tail_n_mail">http://bucardo.org/wiki/Tail_n_mail</a>
+</p>
+
+<h2>PostgreSQL Jobs for March</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+PostgreSQL Conference East 2011: NYC March 22nd - 25th
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<p>
+There will be a large PostgreSQL presence at the MySQL Conference and
+Expo, April 11-14, 2011 in Santa Clara, California.
+<a href="http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql">http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql</a>
+</p>
+
+<p>
+Open Database Camp will be on May 7-9, 2011 in Sardinia, Italy
+<a href="http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html">http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html</a>
+</p>
+
+<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>
+
+<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>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Remove duplicate time-based macros recently added.
+  <a href="http://git.postgresql.org/pg/commitdiff/b051a34fd8877635186ed84a857f2f38cd059468">http://git.postgresql.org/pg/commitdiff/b051a34fd8877635186ed84a857f2f38cd059468</a>
+</p>
+
+<p>
+- Add database comments to template0 and postgres databases, and
+  improve the comments on the template1 database.  No catalog version
+  bump because they are just comments.
+  <a href="http://git.postgresql.org/pg/commitdiff/ddd6ff289f2512f881493b7793853a96955459ff">http://git.postgresql.org/pg/commitdiff/ddd6ff289f2512f881493b7793853a96955459ff</a>
+</p>
+
+<p>
+- Wording adjustment for restart_after_crash entry Specifically,
+  mention that "restart" is disabled by this parameter.
+  <a href="http://git.postgresql.org/pg/commitdiff/df4a9595c20ccd3d3b4ce0e638ca1a5e82546a97">http://git.postgresql.org/pg/commitdiff/df4a9595c20ccd3d3b4ce0e638ca1a5e82546a97</a>
+</p>
+
+<p>
+- Fix spelling error in fuzzystrmatch docs.
+  <a href="http://git.postgresql.org/pg/commitdiff/b774efa9d57a02fbd64dafbe55a059253fbfda4e">http://git.postgresql.org/pg/commitdiff/b774efa9d57a02fbd64dafbe55a059253fbfda4e</a>
+</p>
+
+<p>
+- Add hint suggesting the use of EXECUTE CREATE TABLE ... AS for
+  EXECUTE INTO.
+  <a href="http://git.postgresql.org/pg/commitdiff/2b8364de698b0b425e5d8631a63c91387ee098ef">http://git.postgresql.org/pg/commitdiff/2b8364de698b0b425e5d8631a63c91387ee098ef</a>
+</p>
+
+<p>
+- Adjust doc wording about the casting exceptions for composite types.
+  <a href="http://git.postgresql.org/pg/commitdiff/a858ca19df1491a5082864335efb0fe08e27e960">http://git.postgresql.org/pg/commitdiff/a858ca19df1491a5082864335efb0fe08e27e960</a>
+</p>
+
+<p>
+- Remove unused copy_dir() function from pg_upgrade.
+  <a href="http://git.postgresql.org/pg/commitdiff/898a14e1a0ba845c957f42f205495af932fcf017">http://git.postgresql.org/pg/commitdiff/898a14e1a0ba845c957f42f205495af932fcf017</a>
+</p>
+
+<p>
+- Document guc context values, and reference them from the config doc
+  section.  Tom Lane.
+  <a href="http://git.postgresql.org/pg/commitdiff/e148443ddd95cd29edf4cc1de6188eb9cee029c5">http://git.postgresql.org/pg/commitdiff/e148443ddd95cd29edf4cc1de6188eb9cee029c5</a>
+</p>
+
+<p>
+- Document the all-balls IPv6 address.
+  <a href="http://git.postgresql.org/pg/commitdiff/a7136b7fa2505ec209210803bb74a7946ede337f">http://git.postgresql.org/pg/commitdiff/a7136b7fa2505ec209210803bb74a7946ede337f</a>
+</p>
+
+<p>
+- Document that the timestamp returned by
+  pg_last_xact_replay_timestamp is the time on the primary that the
+  transaction was generated.
+  <a href="http://git.postgresql.org/pg/commitdiff/0191e120e6b427f16aed239c657b9e32c83a0f6d">http://git.postgresql.org/pg/commitdiff/0191e120e6b427f16aed239c657b9e32c83a0f6d</a>
+</p>
+
+<p>
+- Remove "all balls" mention of network address;  change IPv6 address
+  to ::/0.
+  <a href="http://git.postgresql.org/pg/commitdiff/56bb7f2a0275c5e7f17f8fba0d93d12a471869a4">http://git.postgresql.org/pg/commitdiff/56bb7f2a0275c5e7f17f8fba0d93d12a471869a4</a>
+</p>
+
+<p>
+- Initial version of PostgreSQL 9.1 release notes.
+  <a href="http://git.postgresql.org/pg/commitdiff/b03b17c4118345cc89dda1d96cda9ed2313f3ed9">http://git.postgresql.org/pg/commitdiff/b03b17c4118345cc89dda1d96cda9ed2313f3ed9</a>
+</p>
+
+<p>
+- Add SGML markup for keywords, terms, functions, commands, etc.
+  <a href="http://git.postgresql.org/pg/commitdiff/025f4c72f029242a6aaf3f14bb6d7da4ce070f72">http://git.postgresql.org/pg/commitdiff/025f4c72f029242a6aaf3f14bb6d7da4ce070f72</a>
+</p>
+
+<p>
+- Add links to documentation from 9.1 release notes.
+  <a href="http://git.postgresql.org/pg/commitdiff/b2c5b3d1753f1a3e5cb68a610bda27ad768bf061">http://git.postgresql.org/pg/commitdiff/b2c5b3d1753f1a3e5cb68a610bda27ad768bf061</a>
+</p>
+
+<p>
+- Move PITR and StreamingRep up one level of heading in the 9.1
+  release notes.  Remove excessive linking to pg_ctl manual page.
+  Reorder incompatibility sections.
+  <a href="http://git.postgresql.org/pg/commitdiff/c2f4ea469b52e6f7fedff651a4aa0acced873a5f">http://git.postgresql.org/pg/commitdiff/c2f4ea469b52e6f7fedff651a4aa0acced873a5f</a>
+</p>
+
+<p>
+- Reorder some 9.1 release item documentation entries, fix some
+  awkward wording.
+  <a href="http://git.postgresql.org/pg/commitdiff/f670c195b64a97b8b9e9780e80614cd03b9fcadd">http://git.postgresql.org/pg/commitdiff/f670c195b64a97b8b9e9780e80614cd03b9fcadd</a>
+</p>
+
+<p>
+- Fix snapshot isolation level typo in 9.1 release notes. Thom Brown
+  <a href="http://git.postgresql.org/pg/commitdiff/e8f4c240c7065edcbe82e06a2d86c05c8abee67f">http://git.postgresql.org/pg/commitdiff/e8f4c240c7065edcbe82e06a2d86c05c8abee67f</a>
+</p>
+
+<p>
+- Another 9.1 release note typo fix.
+  <a href="http://git.postgresql.org/pg/commitdiff/78fce29628f99a7dd002561dc87904456c992173">http://git.postgresql.org/pg/commitdiff/78fce29628f99a7dd002561dc87904456c992173</a>
+</p>
+
+<p>
+- Markup and wording improvements for 9.1 release notes.
+  <a href="http://git.postgresql.org/pg/commitdiff/62bf9c28061c614df530ac672b1e59f88e805578">http://git.postgresql.org/pg/commitdiff/62bf9c28061c614df530ac672b1e59f88e805578</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Adjust regression test to avoid platform-dependent failure.  We have
+  a test that verifies that max(anyarray) will cope if the array
+  column elements aren't all the same array type.  However, it's now
+  possible for that to produce a collation-related error message
+  instead of the expected one, if the first two column elements happen
+  to be of the same type and it's one that expects to be given
+  collation info.  Tweak the test to ensure this doesn't happen.  Per
+  buildfarm member pika.
+  <a href="http://git.postgresql.org/pg/commitdiff/f12423d75a1181d75bd646869b140ba0c199fa99">http://git.postgresql.org/pg/commitdiff/f12423d75a1181d75bd646869b140ba0c199fa99</a>
+</p>
+
+<p>
+- Improve handling of unknown-type literals in UNION/INTERSECT/EXCEPT.
+  This patch causes unknown-type Consts to be coerced to the resolved
+  output type of the set operation at parse time.  Formerly such
+  Consts were left alone until late in the planning stage.  The
+  disadvantage of that approach is that it disables some
+  optimizations, because the planner sees the set-op leaf query as
+  having different output column types than the overall set-op.  We
+  saw an example of that in a recent performance gripe from Claudio
+  Freire.  Fixing such a Const requires scribbling on the leaf query
+  in transformSetOperationTree, but that should be all right since if
+  the leaf query's semantics depended on that output column, it would
+  already have resolved the unknown to something else.  Most of the
+  bulk of this patch is a simple adjustment of
+  transformSetOperationTree's API so that upper levels can get at the
+  TargetEntry containing a Const to be replaced: it now returns a list
+  of TargetEntries, instead of just the bare expressions.
+  <a href="http://git.postgresql.org/pg/commitdiff/72cfc17aef4fc9aa2de1c82045b7d609c0f2c513">http://git.postgresql.org/pg/commitdiff/72cfc17aef4fc9aa2de1c82045b7d609c0f2c513</a>
+</p>
+
+<p>
+- Revise collation derivation method and expression-tree
+  representation.  All expression nodes now have an explicit
+  output-collation field, unless they are known to only return a
+  noncollatable data type (such as boolean or record).  Also, nodes
+  that can invoke collation-aware functions store a separate field
+  that is the collation value to pass to the function.  This avoids
+  confusion that arises when a function has collatable inputs and
+  noncollatable output type, or vice versa.  Also, replace the
+  parser's on-the-fly collation assignment method with a post-pass
+  over the completed expression tree.  This allows us to use a more
+  complex (and hopefully more nearly spec-compliant) assignment rule
+  without paying for it in extra storage in every expression node.
+  Fix assorted bugs in the planner's handling of collations by making
+  collation one of the defining properties of an EquivalenceClass and
+  by converting CollateExprs into discardable RelabelType nodes during
+  expression preprocessing.
+  <a href="http://git.postgresql.org/pg/commitdiff/b310b6e31ce5aa9e456c43c0e8e93248b0c84c02">http://git.postgresql.org/pg/commitdiff/b310b6e31ce5aa9e456c43c0e8e93248b0c84c02</a>
+</p>
+
+<p>
+- Fix up handling of C/POSIX collations.  Install just one instance of
+  the "C" and "POSIX" collations into pg_collation, rather than one
+  per encoding.  Make these instances exist and do something useful
+  even in machines without locale_t support: to wit, it's now possible
+  to force comparisons and case-folding functions to use C locale in
+  an otherwise non-C database, whether or not the platform has support
+  for using any additional collations.  Fix up severely broken
+  upper/lower/initcap functions, too: the C/POSIX fastpath now does
+  what it is supposed to, and non-default collations are handled
+  correctly in single-byte database encodings.  Merge the two separate
+  collation hashtables that were being maintained in pg_locale.c, and
+  be more wary of the possibility that we fail partway through filling
+  a cache entry.
+  <a href="http://git.postgresql.org/pg/commitdiff/176d5bae1d636fc1e91840b12cbd04c96d638b7e">http://git.postgresql.org/pg/commitdiff/176d5bae1d636fc1e91840b12cbd04c96d638b7e</a>
+</p>
+
+<p>
+- Suppress platform-dependent unused-variable warning.  The local
+  variable "sock" can be unused depending on compilation flags.  But
+  there seems no particular need for it, since the kernel calls can
+  just as easily say port->sock instead.
+  <a href="http://git.postgresql.org/pg/commitdiff/82e4d45bd0ba9c07b8a97f28f939db6d8d564f9a">http://git.postgresql.org/pg/commitdiff/82e4d45bd0ba9c07b8a97f28f939db6d8d564f9a</a>
+</p>
+
+<p>
+- Add some platform-independent tests for the collation feature.
+  There's a lot we can't test very well without platform dependencies,
+  but the C/POSIX collations should now work the same way everywhere.
+  <a href="http://git.postgresql.org/pg/commitdiff/9b095fbea4d6e80e3288e08bd2af4f33aa66875e">http://git.postgresql.org/pg/commitdiff/9b095fbea4d6e80e3288e08bd2af4f33aa66875e</a>
+</p>
+
+<p>
+Magnus Hagander pushed:
+</p>
+
+<p>
+- Remove special case allowing parameters to ident auth for initdb.
+  This was required in pre-8.4 versions to allow the specification of
+  "ident sameuser", but sameuser is no longer required. It could be
+  extended to allow all parameters in the future, but should then
+  apply to all methods and not just ident.
+  <a href="http://git.postgresql.org/pg/commitdiff/01c1a12a5bb4d4f837a542c187ebb2719f9334e8">http://git.postgresql.org/pg/commitdiff/01c1a12a5bb4d4f837a542c187ebb2719f9334e8</a>
+</p>
+
+<p>
+- Properly clear the verbose output of pg_basebackup.  Don't leave
+  partial filename information on the last status or dangling
+  characters if the previous filename was longer than the current one.
+  <a href="http://git.postgresql.org/pg/commitdiff/4a0014806d909bbb490f568af0b8f1ede06149ed">http://git.postgresql.org/pg/commitdiff/4a0014806d909bbb490f568af0b8f1ede06149ed</a>
+</p>
+
+<p>
+- Rename ident authentication over local connections to peer.  This
+  removes an overloading of two authentication options where one is
+  very secure (peer) and one is often insecure (ident). Peer is also
+  the name used in libpq from 9.1 to specify the same type of
+  authentication.  Also make initdb select peer for local connections
+  when ident is chosen, and ident for TCP connections when peer is
+  chosen.  ident keyword in pg_hba.conf is still accepted and maps to
+  peer authentication.
+  <a href="http://git.postgresql.org/pg/commitdiff/6f9192df61e183826211ad2eaf325c6de5cf3656">http://git.postgresql.org/pg/commitdiff/6f9192df61e183826211ad2eaf325c6de5cf3656</a>
+</p>
+
+<p>
+- Misc minor fixes to 9.1 release notes.  Thom Brown
+  <a href="http://git.postgresql.org/pg/commitdiff/0f96ae643c5815d14e39ae8d349be218aae126a8">http://git.postgresql.org/pg/commitdiff/0f96ae643c5815d14e39ae8d349be218aae126a8</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Remove 13 keywords that are used only for ROLE options.  Review by
+  Tom Lane.
+  <a href="http://git.postgresql.org/pg/commitdiff/5ca4dfc79f21828174de3a8bc7d29718d0c52c34">http://git.postgresql.org/pg/commitdiff/5ca4dfc79f21828174de3a8bc7d29718d0c52c34</a>
+</p>
+
+<p>
+- Minor sync rep documentation improvements: Make the name of the ID
+  tag for the GUC entry match the GUC name; Clarify that
+  synchronous_replication waits for xlog flush, not receipt; Mention
+  that synchronous_replication won't wait if max_wal_senders=0.
+  <a href="http://git.postgresql.org/pg/commitdiff/f0f3617135854281bdb79179a895c102d54cb95b">http://git.postgresql.org/pg/commitdiff/f0f3617135854281bdb79179a895c102d54cb95b</a>
+</p>
+
+<p>
+- Corrections to CREATE FOREIGN TABLE documentation.  Omit incorrect =
+  sign, and properly document server_name parameter.  Shigeru Hanada.
+  <a href="http://git.postgresql.org/pg/commitdiff/5f588e20051eb18333f6ea5b46bd779ba1eb8773">http://git.postgresql.org/pg/commitdiff/5f588e20051eb18333f6ea5b46bd779ba1eb8773</a>
+</p>
+
+<p>
+- Tab completion for \pset format and \pset linestyle.  Pavel Stehule
+  <a href="http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9">http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9</a>
+</p>
+
+<p>
+- Tab completion for \pset format and \pset linestyle.  Pavel Stehule
+  <a href="http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9">http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9</a>
+</p>
+
+<p>
+- Fix various possible problems with synchronous replication.  1.
+  Don't ignore query cancel interrupts.  Instead, if the user asks to
+  cancel the query after we've already committed it, but before it's
+  on the standby, just emit a warning and let the COMMIT finish.  2.
+  Don't ignore die interrupts (pg_terminate_backend or fast shutdown).
+  Instead, emit a warning message and close the connection without
+  acknowledging the commit.  Other backends will still see the effect
+  of the commit, but there's no getting around that; it's too late to
+  abort at this point, and ignoring die interrupts altogether doesn't
+  seem like a good idea.  3. If synchronous_standby_names becomes
+  empty, wake up all backends waiting for synchronous replication to
+  complete.  Without this, someone attempting to shut synchronous
+  replication off could easily wedge the entire system instead.  4.
+  Avoid depending on the assumption that if a walsender updates
+  MyProc->syncRepState, we'll see the change even if we read it
+  without holding the lock.  The window for this appears to be quite
+  narrow (and probably doesn't exist at all on machines with strong
+  memory ordering) but protecting against it is practically free, so
+  do that.  5. Remove useless state SYNC_REP_MUST_DISCONNECT, which
+  isn't needed and doesn't actually do anything.  There's still some
+  further work needed here to make the behavior of fast shutdown
+  plausible, but that looks complex, so I'm leaving it for a separate
+  commit.  Review by Fujii Masao.
+  <a href="http://git.postgresql.org/pg/commitdiff/9a56dc3389b9470031e9ef8e45c95a680982e01a">http://git.postgresql.org/pg/commitdiff/9a56dc3389b9470031e9ef8e45c95a680982e01a</a>
+</p>
+
+<p>
+- Add pause_at_recovery_target to recovery.conf.sample; improve docs.
+  Fujii Masao, but with the proposed behavior change reverted, and the
+  rest adjusted accordingly.
+  <a href="http://git.postgresql.org/pg/commitdiff/84abea76f60c5fd1c008b8ddf250b4bc89e288fc">http://git.postgresql.org/pg/commitdiff/84abea76f60c5fd1c008b8ddf250b4bc89e288fc</a>
+</p>
+
+<p>
+- Remove bogus comment.
+  <a href="http://git.postgresql.org/pg/commitdiff/02b1f84e7d2c8921d3ef291469cfd4b7235358f0">http://git.postgresql.org/pg/commitdiff/02b1f84e7d2c8921d3ef291469cfd4b7235358f0</a>
+</p>
+
+<p>
+- Protocol documentation for Hot Standby feedback messages.
+  <a href="http://git.postgresql.org/pg/commitdiff/76dbb4615389e1f44e48074b87be77262143021e">http://git.postgresql.org/pg/commitdiff/76dbb4615389e1f44e48074b87be77262143021e</a>
+</p>
+
+<p>
+- Minor fixes for high availability documentation.  Erik Rijkers and
+  me.
+  <a href="http://git.postgresql.org/pg/commitdiff/f94c6f9c0f05ff70b232e620eb9c420294e90cd3">http://git.postgresql.org/pg/commitdiff/f94c6f9c0f05ff70b232e620eb9c420294e90cd3</a>
+</p>
+
+<p>
+- Remove bogus semicolons in recoveryPausesHere.  Without this, the
+  startup process goes into a tight loop, consuming 100% of one CPU
+  and failing to respond to interrupts.
+  <a href="http://git.postgresql.org/pg/commitdiff/777e8c0015743224cc46f3ce39243b05c6d882ef">http://git.postgresql.org/pg/commitdiff/777e8c0015743224cc46f3ce39243b05c6d882ef</a>
+</p>
+
+<p>
+- Remove ancient -X options to pg_dump, pg_dumpall, pg_restore.  The
+  last version in which these options were documented is now EOL, so
+  it's time to get rid of them for real.  We now use GNU-style long
+  options instead.
+  <a href="http://git.postgresql.org/pg/commitdiff/c5eb835bbffb99518405a1e5bccb58c85e0ab30e">http://git.postgresql.org/pg/commitdiff/c5eb835bbffb99518405a1e5bccb58c85e0ab30e</a>
+</p>
+
+<p>
+- Make synchronous replication query cancel/die messages more
+  consistent.  Per a gripe from Thom Brown about my previous commit in
+  this area, commit 9a56dc3389b9470031e9ef8e45c95a680982e01a.
+  <a href="http://git.postgresql.org/pg/commitdiff/7a37900443b016e0e7c72f6b42327bc05f8b5003">http://git.postgresql.org/pg/commitdiff/7a37900443b016e0e7c72f6b42327bc05f8b5003</a>
+</p>
+
+<p>
+- Woops.  Previous patch to remove -X options missed getopt_long
+  calls().  Noted by Tom Lane.
+  <a href="http://git.postgresql.org/pg/commitdiff/f78ba0a73a60f40270b21c4582f6a7d52fe16739">http://git.postgresql.org/pg/commitdiff/f78ba0a73a60f40270b21c4582f6a7d52fe16739</a>
+</p>
+
+<p>
+- Move synchronous_standbys_defined updates from WAL writer to BG
+  writer.  This is advantageous because the BG writer is alive until
+  much later in the shutdown sequence than WAL writer; we want to make
+  sure that it's possible to shut off synchronous replication during a
+  smart shutdown, else it might not be possible to complete the
+  shutdown at all.  Per very reasonable gripes from Fujii Masao and
+  Simon Riggs.
+  <a href="http://git.postgresql.org/pg/commitdiff/727589995a3e027046f0da7af6ba665b0b47f89f">http://git.postgresql.org/pg/commitdiff/727589995a3e027046f0da7af6ba665b0b47f89f</a>
+</p>
+
+<p>
+- Fix possible "tuple concurrently updated" error in ALTER TABLE.
+  When adding an inheritance parent to a table, an AccessShareLock on
+  the parent isn't strong enough to prevent trouble, so take
+  ShareUpdateExclusiveLock instead.  Since this is a behavior change,
+  albeit a fairly unobtrusive one, and since we have only one report
+  from the field, no back-patch.  Report by Jon Nelson, analysis by
+  Alvaro Herrera, fix by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/fbcf4b92aa64d4577bcf25925b055316b978744a">http://git.postgresql.org/pg/commitdiff/fbcf4b92aa64d4577bcf25925b055316b978744a</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Use correct PATH separator for Cygwin in pg_regress.c.  This has
+  been broken for years, and I'm not sure why it has not been noticed
+  before, but now a very modern Cygwin breaks on it, and the fix is
+  clearly correct. Backpatching to all live branches.
+  <a href="http://git.postgresql.org/pg/commitdiff/5b079cb248b91cbd5bc577ea96802ec466f40b38">http://git.postgresql.org/pg/commitdiff/5b079cb248b91cbd5bc577ea96802ec466f40b38</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Raise maximum value of several timeout parameters The maximum value
+  of deadlock_timeout, max_standby_archive_delay,
+  max_standby_streaming_delay, log_min_duration_statement, and
+  log_autovacuum_min_duration was INT_MAX/1000 milliseconds, which is
+  about 35min, which is too short for some practical uses.  Raise the
+  maximum value to INT_MAX; the code that uses the parameters already
+  supports that just fine.
+  <a href="http://git.postgresql.org/pg/commitdiff/8c0a5eb78af00ec4720e693feaba70b5a73205d1">http://git.postgresql.org/pg/commitdiff/8c0a5eb78af00ec4720e693feaba70b5a73205d1</a>
+</p>
+
+<p>
+Alvaro Herrera pushed:
+</p>
+
+<p>
+- Fix PL/Python memory leak involving array slices.  Report and patch
+  from Daniel Popowich, bug #5842 (with some debugging help from Alex
+  Hunsaker)
+  <a href="http://git.postgresql.org/pg/commitdiff/1c249fcfcc331d589a2fa1574e16c0ef3d1547ce">http://git.postgresql.org/pg/commitdiff/1c249fcfcc331d589a2fa1574e16c0ef3d1547ce</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Fujii Masao sent in another revision of the replication server timeout
+patch.
+</p>
+
+<p>
+Robert Haas sent in two revisions of a patch intended to fix some
+infelicities in syncrep.
+</p>
+
+<p>
+Roman Zotov sent in a patch to turn PREFERRED for type from a boolean
+to an int2, which allows for an expression of precedence.
+</p>
+
+<p>
+Thom Brown sent in a patch to allow users to set a default database
+name other than postgres in initdb.
+</p>
+
+<p>
+Piyush Newe sent in a patch intended to fix some infelicities in
+century handling in to_date.
+</p>
+
+<p>
+Heikki Linnakangas sent in another revision of the patch to enable
+taking multiple base backups.
+</p>
+
+<p>
+Radoslaw Smogura sent in two revisions of a patch to add a second
+level buffer cache.
+</p>
+
+<p>
+Kevin Grittner sent in two revisions of a patch intended to fix an
+issue in SSI.
+</p>
+
+<p>
+Nikhil Sontakke sent in two revisions of a patch to fix an issue with
+a VACUUM FULL deadlock.
+</p>
+
+<p>
+Jan Urbanski sent in another revision of the patch to add PL/PythonU
+tracebacks.
+
+</p>
+