From 659d11786c206986f0e9dd31c56a5139076fab86 Mon Sep 17 00:00:00 2001
From: David Fetter <david@fetter.org>
Date: Mon, 1 Aug 2011 05:21:38 +0000
Subject: [PATCH] PostgreSQL Weekly News July 31, 2011

git-svn-id: file:///Users/dpage/pgweb/svn-repo/trunk@2869 8f5c7a92-453e-0410-a47f-ad33c8a6b003
---
 portal/files/weeklynews.xml                   |  47 +-
 portal/template/en/community/weeklynews.html  |   2 +
 .../en/community/weeklynews/pwn20110724.html  | 531 ++++++++++++++++++
 .../en/community/weeklynews/pwn20110731.html  | 342 +++++++++++
 4 files changed, 899 insertions(+), 23 deletions(-)
 create mode 100644 portal/template/en/community/weeklynews/pwn20110724.html
 create mode 100644 portal/template/en/community/weeklynews/pwn20110731.html

diff --git a/portal/files/weeklynews.xml b/portal/files/weeklynews.xml
index ef6f5512..b268f7d0 100644
--- a/portal/files/weeklynews.xml
+++ b/portal/files/weeklynews.xml
@@ -10,6 +10,30 @@
 <description></description>
 <language>en</language>
 
+<item>
+<title>PostgreSQL Weekly News July 31st 2011</title>
+<description>
+ODB 1.5.0, an ORM for C++, supports PostgreSQL.
+&#x3C;a href=&#x22;http://www.codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/&#x22;&#x3E;http://www.codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/&#x3C;/a&#x3E;                                                                                      
+
+
+</description>
+<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110731</guid>
+<pubDate>Sun, 31 Jul 2011 00:00:00 PST</pubDate>
+</item>
+<item>
+<title>PostgreSQL Weekly News July 24th 2011</title>
+<description>
+Postgres Open 2011, a conference focused on disruption of the database
+industry through PostgreSQL, will take place September 14-16, 2011 in
+Chicago, Illinois at the Westin Michigan Avenue hotel.
+&#x3C;a href=&#x22;http://postgresopen.org&#x22;&#x3E;http://postgresopen.org&#x3C;/a&#x3E;
+
+
+</description>
+<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110724</guid>
+<pubDate>Sun, 24 Jul 2011 00:00:00 PST</pubDate>
+</item>
 <item>
 <title>PostgreSQL Weekly News July 17th 2011</title>
 <description>
@@ -107,28 +131,5 @@ you don&#x27;t have to wait until then to review a patch.
 <guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110522</guid>
 <pubDate>Sun, 22 May 2011 00:00:00 PST</pubDate>
 </item>
-<item>
-<title>PostgreSQL Weekly News May 15th 2011</title>
-<description>
-PostgreSQL Conference China 2011 will be held in Guangzhou on July
-15-16, 2011.
-&#x3C;a href=&#x22;http://wiki.postgresql.org/wiki/Pgconchina2011&#x22;&#x3E;http://wiki.postgresql.org/wiki/Pgconchina2011&#x3C;/a&#x3E;
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110515</guid>
-<pubDate>Sun, 15 May 2011 00:00:00 PST</pubDate>
-</item>
-<item>
-<title>PostgreSQL Weekly News May 8th 2011</title>
-<description>
-PostgreSQL 9.1 beta 1 is out.  Test!
-&#x3C;a href=&#x22;http://www.postgresql.org/developer/beta&#x22;&#x3E;http://www.postgresql.org/developer/beta&#x3C;/a&#x3E;
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110508</guid>
-<pubDate>Sun, 08 May 2011 00:00:00 PST</pubDate>
-</item>
 </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 deae6001..b5197a81 100644
--- a/portal/template/en/community/weeklynews.html
+++ b/portal/template/en/community/weeklynews.html
@@ -11,6 +11,8 @@ Weekly News
 <p>Here is the <a href="http://www.postgresql.org/files/weeklynews.xml">RSS feed</a>.</p>
 
 <ul>
+    <li><a href="/community/weeklynews/pwn20110731">July 31st 2011</a></li>
+    <li><a href="/community/weeklynews/pwn20110724">July 24th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110717">July 17th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110703">July 3rd 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110626">June 26th 2011</a></li>
diff --git a/portal/template/en/community/weeklynews/pwn20110724.html b/portal/template/en/community/weeklynews/pwn20110724.html
new file mode 100644
index 00000000..d8d52412
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110724.html
@@ -0,0 +1,531 @@
+<!-- BEGIN page_title_block -->
+Weekly News - July 24 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - July 24 2011</h1>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+pgbuildfarm client 4.6 released.
+<a href="https://github.com/PGBuildFarm/client-code">https://github.com/PGBuildFarm/client-code</a>
+</p>
+
+<h2>PostgreSQL Jobs for July</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-07/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-07/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+PGDay Porto Alegre will be on August 19, 2011 in Porto Alegre, RS, Brazil.
+<a href="http://www.postgresql.org.br/eventos/2011/pgday/rs">http://www.postgresql.org.br/eventos/2011/pgday/rs</a>
+</p>
+
+<p>
+Postgres Open 2011, a conference focused on disruption of the database
+industry through PostgreSQL, will take place September 14-16, 2011 in
+Chicago, Illinois at the Westin Michigan Avenue hotel.
+<a href="http://postgresopen.org">http://postgresopen.org</a>
+</p>
+
+<p>
+PG-Day Denver 2011 will be held on Friday, October 21st, 2011 at
+the Auraria Campus near downtown Denver, Colorado.
+<a href="http://pgday.consistentstate.com/">http://pgday.consistentstate.com/</a>
+</p>
+
+<p>
+PostgreSQL Conference West (#PgWest) will be held September 27th-30th,
+2011 at the San Jose Convention center in San Jose, California, USA.
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<p>
+PostgreSQL Conference Europe 2011 will be held on October 18-21 in
+Amsterdam.
+<a href="http://2011.pgconf.eu/">http://2011.pgconf.eu/</a>
+</p>
+
+<p>
+pgbr will be in Sao Paulo, Brazil November 3-4, 2011.
+<a href="http://pgbr.postgresql.org.br/">http://pgbr.postgresql.org.br/</a>
+</p>
+
+<p>
+PGConf.DE 2011 is the German-speaking PostgreSQL Conference and will
+take place on November 11th in the Rheinisches Industriemuseum in
+Oberhausen, Germany.  Call for Papers is open.
+<a href="http://2011.pgconf.de/">http://2011.pgconf.de/</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>
+Robert Haas pushed:
+</p>
+
+<p>
+- Add pg_opfamily_is_visible.  We already have similar functions for
+  many other object types, including operator classes, so it seems
+  like we should have this one, too.  Extracted from a larger patch by
+  Josh Kupershmidt
+  <a href="http://git.postgresql.org/pg/commitdiff/b59d2fe4970e689a50e802960ef0812acaf88221">http://git.postgresql.org/pg/commitdiff/b59d2fe4970e689a50e802960ef0812acaf88221</a>
+</p>
+
+<p>
+- Create a "fast path" for acquiring weak relation locks.  When an
+  AccessShareLock, RowShareLock, or RowExclusiveLock is requested on
+  an unshared database relation, and we can verify that no conflicting
+  locks can possibly be present, record the lock in a per-backend
+  queue, stored within the PGPROC, rather than in the primary lock
+  table.  This eliminates a great deal of contention on the lock
+  manager LWLocks.  This patch also refactors the interface between
+  GetLockStatusData() and pg_lock_status() to be a bit more abstract,
+  so that we don't rely so heavily on the lock manager's internal
+  representation details.  The new fast path lock structures don't
+  have a LOCK or PROCLOCK structure to return, so we mustn't depend on
+  that for purposes of listing outstanding locks.  Review by Jeff
+  Davis.
+  <a href="http://git.postgresql.org/pg/commitdiff/3cba8999b343648c4c528432ab3d51400194e93b">http://git.postgresql.org/pg/commitdiff/3cba8999b343648c4c528432ab3d51400194e93b</a>
+</p>
+
+<p>
+- Avoid index rebuild for no-rewrite ALTER TABLE .. ALTER TYPE.  Noah
+  Misch.  Review and minor cosmetic changes by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/367bc426a1c22b9f6badb06cd41fc438fd034639">http://git.postgresql.org/pg/commitdiff/367bc426a1c22b9f6badb06cd41fc438fd034639</a>
+</p>
+
+<p>
+- Remove superfluous variable.  Reported by Peter Eisentraut.
+  <a href="http://git.postgresql.org/pg/commitdiff/cdd61237d6265fa355afa772ca3eee39e4905bcb">http://git.postgresql.org/pg/commitdiff/cdd61237d6265fa355afa772ca3eee39e4905bcb</a>
+</p>
+
+<p>
+- Some refinement for the "fast path" lock patch.  1. In
+  GetLockStatusData, avoid initializing instance before we've ensured
+  that the array is large enough.  Otherwise, if repalloc moves the
+  block around, we're hosed.  2. Add the word "Relation" to the name
+  of some identifiers, to avoid assuming that the fast-path mechanism
+  will only ever apply to relations (though these particular parts
+  certainly will).  Some of the macros could possibly use similar
+  treatment, but the names are getting awfully long already.  3. Add a
+  missing word to comment in AtPrepare_Locks().
+  <a href="http://git.postgresql.org/pg/commitdiff/8e5ac74c1249820ca55481223a95b9124b4a4f95">http://git.postgresql.org/pg/commitdiff/8e5ac74c1249820ca55481223a95b9124b4a4f95</a>
+</p>
+
+<p>
+- Minor improvement to pg_seclabel documentation.  This is a bit more
+  consistent with the way pg_description is documented, and also
+  include a useful cross-link.
+  <a href="http://git.postgresql.org/pg/commitdiff/550cd074f9436c0500c1718e792d3d72a304bf8b">http://git.postgresql.org/pg/commitdiff/550cd074f9436c0500c1718e792d3d72a304bf8b</a>
+</p>
+
+<p>
+- Improve sepgsql and SECURITY LABEL documentation.  KaiGai Kohei,
+  based on feedback from Yeb Havinga, with some corrections by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/d79a601fd9ec59772395d16b33fe79296021a350">http://git.postgresql.org/pg/commitdiff/d79a601fd9ec59772395d16b33fe79296021a350</a>
+</p>
+
+<p>
+- Support SECURITY LABEL on databases, tablespaces, and roles.  This
+  requires a new shared catalog, pg_shseclabel.  Along the way, fix
+  the security_label regression tests so that they don't monkey with
+  the labels of any pre-existing objects.  This is unlikely to matter
+  in practice, since only the label for the "dummy" provider was being
+  manipulated.  But this way still seems cleaner.  KaiGai Kohei, with
+  fairly extensive hacking by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/463f2625a5fb183b6a8925ccde98bb3889f921d9">http://git.postgresql.org/pg/commitdiff/463f2625a5fb183b6a8925ccde98bb3889f921d9</a>
+</p>
+
+<p>
+- Unbreak unlogged tables.  I broke this in commit
+  5da79169d3e9f0fab47da03318c44075b3f824c5, which was obviously
+  insufficiently well tested.  Add some regression tests in the hope
+  of making future slip-ups more likely to be noticed.
+  <a href="http://git.postgresql.org/pg/commitdiff/6f1be5a67a758499beab0082b6e63b3040913268">http://git.postgresql.org/pg/commitdiff/6f1be5a67a758499beab0082b6e63b3040913268</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Remove claim that the project is not represented in the SQL working
+  group We have a few people involved there now.
+  <a href="http://git.postgresql.org/pg/commitdiff/7ed8f6c517ba6bada6bfb9a4dd4216e3b97bc2ba">http://git.postgresql.org/pg/commitdiff/7ed8f6c517ba6bada6bfb9a4dd4216e3b97bc2ba</a>
+</p>
+
+<p>
+- Note that information_schema.sql_languages was removed in SQL:2008
+  <a href="http://git.postgresql.org/pg/commitdiff/3835855589d8fe8bd5ea0fa51a5a539756223612">http://git.postgresql.org/pg/commitdiff/3835855589d8fe8bd5ea0fa51a5a539756223612</a>
+</p>
+
+<p>
+- Put inline declaration before return type.  gcc -Wextra complains
+  that the other way around is obsolescent, and this was the only
+  place where it was written in this order.
+  <a href="http://git.postgresql.org/pg/commitdiff/bf6be7af2532da6674dcb9335c0953044a787427">http://git.postgresql.org/pg/commitdiff/bf6be7af2532da6674dcb9335c0953044a787427</a>
+</p>
+
+<p>
+- Change debug message from ereport to elog
+  <a href="http://git.postgresql.org/pg/commitdiff/30f854537d0d2e9220976fe7016c909daabea612">http://git.postgresql.org/pg/commitdiff/30f854537d0d2e9220976fe7016c909daabea612</a>
+</p>
+
+<p>
+- Fix typo
+  <a href="http://git.postgresql.org/pg/commitdiff/6307fff3586294214e3f256035b82bbba9a9054a">http://git.postgresql.org/pg/commitdiff/6307fff3586294214e3f256035b82bbba9a9054a</a>
+</p>
+
+<p>
+- Change EDITOR_LINENUMBER_SWITCH to an environment variable.  Also
+  change "switch" to "arg" because "switch" is a bit of a sloppy term.
+  So the environment variable is called PSQL_EDITOR_LINENUMBER_ARG.
+  Set "+" as hardcoded default value on Unix (since "vi" is the
+  hardcoded default editor), so many users won't have to configure
+  this at all.  Move the documentation around a bit to centralize the
+  editor configuration under environment variables, rather than
+  repeating bits of it under every backslash command that invokes an
+  editor.
+  <a href="http://git.postgresql.org/pg/commitdiff/79b3ca06d820032ad84446e0a021b56422172d86">http://git.postgresql.org/pg/commitdiff/79b3ca06d820032ad84446e0a021b56422172d86</a>
+</p>
+
+<p>
+Michael Meskes pushed:
+</p>
+
+<p>
+- Made ecpglib write double with a precision of 15 digits.  Patch
+  originally by Akira Kurosawa <kurosawa-akira@mxc.nes.nec.co.jp>.
+  <a href="http://git.postgresql.org/pg/commitdiff/8f8a273c4d2433de57f6f0356f44ab47b7387641">http://git.postgresql.org/pg/commitdiff/8f8a273c4d2433de57f6f0356f44ab47b7387641</a>
+</p>
+
+<p>
+- Adapted expected result for latest change to ecpglib.
+  <a href="http://git.postgresql.org/pg/commitdiff/3406dd22fdd794d90c75a1272a57db8faa7c826d">http://git.postgresql.org/pg/commitdiff/3406dd22fdd794d90c75a1272a57db8faa7c826d</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Add GET STACKED DIAGNOSTICS plpgsql command to retrieve exception
+  info.  This is more SQL-spec-compliant, more easily extensible, and
+  better performing than the old method of inventing special
+  variables.  Pavel Stehule, reviewed by Shigeru Hanada and David
+  Wheeler
+  <a href="http://git.postgresql.org/pg/commitdiff/3d4890c0c5d27dfdf7d1a8816d7bdcdba3c39d21">http://git.postgresql.org/pg/commitdiff/3d4890c0c5d27dfdf7d1a8816d7bdcdba3c39d21</a>
+</p>
+
+<p>
+- Rewrite libxml error handling to be more robust.  libxml reports
+  some errors (like invalid xmlns attributes) via the error handler
+  hook, but still returns a success indicator to the library caller.
+  This causes us to miss some errors that are important to report.
+  Since the "generic" error handler hook doesn't know whether the
+  message it's getting is for an error, warning, or notice, stop using
+  that and instead start using the "structured" error handler hook,
+  which gets enough information to be useful.  While at it, arrange to
+  save and restore the error handler hook setting in each libxml-using
+  function, rather than assuming we can set and forget the hook.  This
+  should improve the odds of working nicely with third-party libraries
+  that also use libxml.  In passing, volatile-ize some local variables
+  that get modified within PG_TRY blocks.  I noticed this while
+  testing with an older gcc version than I'd previously tried to
+  compile xml.c with.  Florian Pflug and Tom Lane, with extensive
+  review/testing by Noah Misch
+  <a href="http://git.postgresql.org/pg/commitdiff/cacd42d62cb2ddf32135b151f627780a5509780f">http://git.postgresql.org/pg/commitdiff/cacd42d62cb2ddf32135b151f627780a5509780f</a>
+</p>
+
+<p>
+- Ensure that xpath() escapes special characters in string values.
+  Without this it's possible for the output to not be legal XML, as
+  illustrated by the added regression test cases.  NB: this change
+  will need to be called out as an incompatibility in the 9.2 release
+  notes, since it's possible somebody was relying on the old behavior,
+  even though it's clearly wrong.  Florian Pflug, reviewed by Radoslaw
+  Smogura
+  <a href="http://git.postgresql.org/pg/commitdiff/aaf15e5c1cf8d2c27d2f9841343f00027762cb4e">http://git.postgresql.org/pg/commitdiff/aaf15e5c1cf8d2c27d2f9841343f00027762cb4e</a>
+</p>
+
+<p>
+- Make xpath() do something useful with XPath expressions that return
+  scalars.  Previously, xpath() simply returned an empty array if the
+  expression did not yield a node set.  This is useless for
+  expressions that return scalars, such as one with name() at the top
+  level.  Arrange to return the scalar value as a single-element xml
+  array, instead.  (String values will be suitably escaped.) This
+  change will also cause xpath_exists() to return true, not false, for
+  such expressions.  Florian Pflug, reviewed by Radoslaw Smogura
+  <a href="http://git.postgresql.org/pg/commitdiff/0ce7676aa03a2501fde949fea211ba5cd84c2ded">http://git.postgresql.org/pg/commitdiff/0ce7676aa03a2501fde949fea211ba5cd84c2ded</a>
+</p>
+
+<p>
+- Fix PQsetvalue() to avoid possible crash when adding a new tuple.
+  PQsetvalue unnecessarily duplicated the logic in pqAddTuple, and
+  didn't duplicate it exactly either --- pqAddTuple does not care what
+  is in the tuple-pointer array positions beyond the last valid entry,
+  whereas the code in PQsetvalue assumed such positions would contain
+  NULL.  This led to possible crashes if PQsetvalue was applied to a
+  PGresult that had previously been enlarged with pqAddTuple, for
+  instance one built from a server query.  Fix by relying on
+  pqAddTuple instead of duplicating logic, and not assuming anything
+  about the contents of res->tuples[res->ntups].  Back-patch to 8.4,
+  where PQsetvalue was introduced.  Andrew Chernow
+  <a href="http://git.postgresql.org/pg/commitdiff/a9f0dbc39df88ea7672352d3e7070d2603491bec">http://git.postgresql.org/pg/commitdiff/a9f0dbc39df88ea7672352d3e7070d2603491bec</a>
+</p>
+
+<p>
+- Rethink behavior of CREATE OR REPLACE during CREATE EXTENSION.  The
+  original implementation simply did nothing when replacing an
+  existing object during CREATE EXTENSION.  The folly of this was
+  exposed by a report from Marc Munro: if the existing object belongs
+  to another extension, we are left in an inconsistent state.  We
+  should insist that the object does not belong to another extension,
+  and then add it to the current extension if not already a member.
+  <a href="http://git.postgresql.org/pg/commitdiff/988cccc620dd8c16d77f88ede167b22056176324">http://git.postgresql.org/pg/commitdiff/988cccc620dd8c16d77f88ede167b22056176324</a>
+</p>
+
+<p>
+- Use OpenSSL's SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER flag.  This
+  disables an entirely unnecessary "sanity check" that causes failures
+  in nonblocking mode, because OpenSSL complains if we move or compact
+  the write buffer.  The only actual requirement is that we not modify
+  pending data once we've attempted to send it, which we don't.  Per
+  testing and research by Martin Pihlak, though this fix is a lot
+  simpler than his patch.  I put the same change into the backend,
+  although it's less clear whether it's necessary there.  We do use
+  nonblock mode in some situations in streaming replication, so seems
+  best to keep the same behavior in the backend as in libpq.
+  Back-patch to all supported releases.
+  <a href="http://git.postgresql.org/pg/commitdiff/d0c23026b2499ba9d6797359241ade076a5a677d">http://git.postgresql.org/pg/commitdiff/d0c23026b2499ba9d6797359241ade076a5a677d</a>
+</p>
+
+<p>
+- Improve libpq's error reporting for SSL failures.  In many cases,
+  pqsecure_read/pqsecure_write set up useful error messages, which
+  were then overwritten with useless ones by their callers.  Fix this
+  by defining the responsibility to set an error message to be
+  entirely that of the lower-level function when using SSL.
+  Back-patch to 8.3; the code is too different in 8.2 to be worth the
+  trouble.
+  <a href="http://git.postgresql.org/pg/commitdiff/fee476da952a1f02f7ccf6e233fb4824c2bf6af4">http://git.postgresql.org/pg/commitdiff/fee476da952a1f02f7ccf6e233fb4824c2bf6af4</a>
+</p>
+
+<p>
+- Fix previous patch so it also works if not USE_SSL (mea culpa).  On
+  balance, the need to cover this case changes my mind in favor of
+  pushing all error-message generation duties into the two fe-secure.c
+  routines.  So do it that way.
+  <a href="http://git.postgresql.org/pg/commitdiff/bcf23ba4bf8323f875168c5dbc93265a140753e8">http://git.postgresql.org/pg/commitdiff/bcf23ba4bf8323f875168c5dbc93265a140753e8</a>
+</p>
+
+<p>
+Simon Riggs pushed:
+</p>
+
+<p>
+- Cascading replication feature for streaming log-based replication.
+  Standby servers can now have WALSender processes, which can work
+  with either WALReceiver or archive_commands to pass data.  Fully
+  updated docs, including new conceptual terms of sending server,
+  upstream and downstream servers.  WALSenders terminated when promote
+  to master.  Fujii Masao, review, rework and doc rewrite by Simon
+  Riggs
+  <a href="http://git.postgresql.org/pg/commitdiff/5286105800c7d5902f98f32e11b209c471c0c69c">http://git.postgresql.org/pg/commitdiff/5286105800c7d5902f98f32e11b209c471c0c69c</a>
+</p>
+
+<p>
+- Introduce sending servers as new category for replication params.
+  Fujii Masao
+  <a href="http://git.postgresql.org/pg/commitdiff/4bd8ed31b76fde16ee00c123751e25019e4d9854">http://git.postgresql.org/pg/commitdiff/4bd8ed31b76fde16ee00c123751e25019e4d9854</a>
+</p>
+
+<p>
+- Minor doc additions for cascading replication.
+  <a href="http://git.postgresql.org/pg/commitdiff/6ba77bce9378cb9c5fb89a4d30bf77c2a17b0d64">http://git.postgresql.org/pg/commitdiff/6ba77bce9378cb9c5fb89a4d30bf77c2a17b0d64</a>
+</p>
+
+<p>
+- Remove O(N^2) performance issue with multiple SAVEPOINTs.
+  Subtransaction locks now released en masse at main commit, rather
+  than repeatedly re-scanning for locks as we ascend the nested
+  transaction tree.  Split transaction state TBLOCK_SUBEND into two
+  states, TBLOCK_SUBCOMMIT and TBLOCK_SUBRELEASE to allow the commit
+  path to be optimised using the existing code in
+  ResourceOwnerRelease() which appears to have been intended for this
+  usage, judging from comments therein.
+  <a href="http://git.postgresql.org/pg/commitdiff/7cb7122800ec996d4849ce9b4ad3065db19a2aae">http://git.postgresql.org/pg/commitdiff/7cb7122800ec996d4849ce9b4ad3065db19a2aae</a>
+</p>
+
+<p>
+Alvaro Herrera pushed:
+</p>
+
+<p>
+- Add expected regress output on stricter isolation levels.  These new
+  files allow the new FK tests on isolationtester to pass on the
+  serializable and repeatable read isolation levels (which are
+  untested by the buildfarm).  Author: Kevin Grittner Reviewed by Noah
+  Misch
+  <a href="http://git.postgresql.org/pg/commitdiff/a0eae1a2eeb6c0e9deffeccad2f9921d8e561fb5">http://git.postgresql.org/pg/commitdiff/a0eae1a2eeb6c0e9deffeccad2f9921d8e561fb5</a>
+</p>
+
+<p>
+- Make isolationtester more robust on locked commands.  Noah Misch
+  diagnosed the buildfarm problems in the isolation tests partly as
+  failure to differentiate backends properly; the old code was using
+  backend IDs, which is not good enough because a new backend might
+  use an already used ID.  Use PIDs instead.  Also, the code was
+  purposely careless about other concurrent activity, because it isn't
+  expected; and in fact, it doesn't affect the vast majority of the
+  time.  However, it can be observed that autovacuum can block tables
+  for long enough to cause sporadic failures.  The new code accounts
+  for that by ignoring locks held by processes not explicitly declared
+  in our spec file.  Author: Noah Misch
+  <a href="http://git.postgresql.org/pg/commitdiff/c8dfc892327b1a1e14efe110b0f1f267ef56c7a9">http://git.postgresql.org/pg/commitdiff/c8dfc892327b1a1e14efe110b0f1f267ef56c7a9</a>
+</p>
+
+<p>
+- Increase deadlock_timeout to 100ms in FK isolation tests.  The
+  previous value of 20ms is dangerously close to the time actually
+  spent just waiting for the deadlock to happen, so on occasion it
+  causes the test to fail simply because the other session didn't get
+  to run early enough, not managing to cause the deadlock that needs
+  to be detected.  With this new value, it's expected that most
+  machines on normal load will be able to pass the test.  Author: Noah
+  Misch
+  <a href="http://git.postgresql.org/pg/commitdiff/d6db0e4e0e382cd5683a767424d05a0361af232a">http://git.postgresql.org/pg/commitdiff/d6db0e4e0e382cd5683a767424d05a0361af232a</a>
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- In pg_upgrade, use pg_strudup(), for consistency.
+  <a href="http://git.postgresql.org/pg/commitdiff/6b43fddee4cbc1bca71546e15e898d19bee7bcb1">http://git.postgresql.org/pg/commitdiff/6b43fddee4cbc1bca71546e15e898d19bee7bcb1</a>
+</p>
+
+<p>
+- In pg_upgrade, fix the -l/log option to work on Windows.  Also,
+  double-quote the log file name in all places, to allow (on all
+  platforms) log file names with spaces.  Back patch to 9.0 and 9.1.
+  <a href="http://git.postgresql.org/pg/commitdiff/17a16eeb7c4fd0c6dce80521247a20d76706b2bb">http://git.postgresql.org/pg/commitdiff/17a16eeb7c4fd0c6dce80521247a20d76706b2bb</a>
+</p>
+
+<p>
+- In pg_upgrade, add C comment about why we don't try to do shared
+  file writes for logging.
+  <a href="http://git.postgresql.org/pg/commitdiff/43aa40e1551b9e8d30b376de6d6a9b976ae54332">http://git.postgresql.org/pg/commitdiff/43aa40e1551b9e8d30b376de6d6a9b976ae54332</a>
+</p>
+
+<p>
+- In pg_upgrade on Windows, check if the directory is writable by
+  actually creating and removing a file because access() doesn't work
+  on that platform.  Backpatch to 9.1 where this check was added.
+  <a href="http://git.postgresql.org/pg/commitdiff/081a5518c0a7dcccfc76a12ae9d593648b68ce53">http://git.postgresql.org/pg/commitdiff/081a5518c0a7dcccfc76a12ae9d593648b68ce53</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Unbreak Windows builds broken by EDITOR_LINENUMBER_ARG change.
+  <a href="http://git.postgresql.org/pg/commitdiff/e399eb74d96270bf1d4a0bb9f4503cac3d90c1e2">http://git.postgresql.org/pg/commitdiff/e399eb74d96270bf1d4a0bb9f4503cac3d90c1e2</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Alexander Korotkov sent in two more revisions of the patch to do fast
+GiST index builds.
+</p>
+
+<p>
+Peter Eisentraut sent in a patch to allow reporting of hostnames from
+pg_hba.conf in error messages.
+</p>
+
+<p>
+KaiGai Kohei and Yeb Havinga traded revisions of the patch to create a
+userspace access vector cache.
+</p>
+
+<p>
+Josh Kupershmidt sent in two more revisions of the patch to allow
+psql's \dd to show constraint comments.
+</p>
+
+<p>
+Robert Haas sent in another revision of a patch to enable lazy vxid
+locks.
+</p>
+
+<p>
+Kevin Grittner sent in two revisions of a patch to fix bug 6123.
+</p>
+
+<p>
+Robert Haas sent in a patch to eliminate sinval in several places
+where it was slowing things down.
+</p>
+
+<p>
+Alvaro Herrera sent in a patch to catalog NOT NULL constraints.
+</p>
+
+<p>
+Josh Kupershmidt sent in a patch to fix some wrong descriptions in
+\d+, and an patch for 8.4 which documents the fact that it's possible
+to put comments on index columns.
+</p>
+
+<p>
+Hitoshi Harada and Yeb Havinga traded patches to optimize aggregates
+in JOINs.
+</p>
+
+<p>
+Josh Kupershmidt sent in another revision of the patch to fix describe
+comments in psql.
+</p>
+
+<p>
+Laurenz Albe sent in a doc patch explaining more about how foreign
+data wrappers work from the implementor's point of view.
+</p>
+
+<p>
+Florian Pflug sent in a patch, per discussion around a similar issue
+in JSON, which changes behavior in cases of non-UTF8-encoded content.
+</p>
+
+<p>
+Andrew Dunstan sent in a patch to clean up python usage in the source
+code for PL/PythonU.
+
+</p>
+
diff --git a/portal/template/en/community/weeklynews/pwn20110731.html b/portal/template/en/community/weeklynews/pwn20110731.html
new file mode 100644
index 00000000..d6f94b70
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110731.html
@@ -0,0 +1,342 @@
+<!-- BEGIN page_title_block -->
+Weekly News - July 31 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - July 31 2011</h1>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+Database Master 4, a GUI management and reporting tool which supports
+PostgreSQL, released.
+<a href="http://www.nucleonsoftware.com/">http://www.nucleonsoftware.com/</a>
+</p>
+
+<p>
+ODB 1.5.0, an ORM for C++, supports PostgreSQL.
+<a href="http://www.codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/">http://www.codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/</a>                                                                                      
+</p>
+
+<p>
+pgfincore, 1.0, a set of functions to handle low-level management of
+relations using mincore to explore cache memory, released.
+<a href="http://pgfoundry.org/projects/pgfincore/">http://pgfoundry.org/projects/pgfincore/</a>
+</p>
+
+<p>
+Slony-I 2.0.7, a master-to-multiple-cascading-replica system for
+PostgreSQL, released.
+<a href="http://www.slony.info/">http://www.slony.info/</a>
+</p>
+
+<p>
+Version 1.19.3 of tail_n_mail, a Postgres log watcher program, released.
+<a href="http://bucardo.org/wiki/Tail_n_mail">http://bucardo.org/wiki/Tail_n_mail</a>
+</p>
+
+<p>
+Version 4.4.6 of Bucardo, a Postgres multi-master replication system, released.
+<a href="http://bucardo.org/wiki/Bucardo">http://bucardo.org/wiki/Bucardo</a>
+</p>
+
+<h2>PostgreSQL Jobs for July</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-07/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-07/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+PGDay Porto Alegre will be on August 19, 2011 in Porto Alegre, RS, Brazil.
+<a href="http://www.postgresql.org.br/eventos/2011/pgday/rs">http://www.postgresql.org.br/eventos/2011/pgday/rs</a>
+</p>
+
+<p>
+Postgres Open 2011, a conference focused on disruption of the database
+industry through PostgreSQL, will take place September 14-16, 2011 in
+Chicago, Illinois at the Westin Michigan Avenue hotel.
+<a href="http://postgresopen.org">http://postgresopen.org</a>
+</p>
+
+<p>
+PG-Day Denver 2011 will be held on Friday, October 21st, 2011 at
+the Auraria Campus near downtown Denver, Colorado.
+<a href="http://pgday.consistentstate.com/">http://pgday.consistentstate.com/</a>
+</p>
+
+<p>
+PostgreSQL Conference West (#PgWest) will be held September 27th-30th,
+2011 at the San Jose Convention center in San Jose, California, USA.
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<p>
+PostgreSQL Conference Europe 2011 will be held on October 18-21 in
+Amsterdam.
+<a href="http://2011.pgconf.eu/">http://2011.pgconf.eu/</a>
+</p>
+
+<p>
+pgbr will be in Sao Paulo, Brazil November 3-4, 2011.
+<a href="http://pgbr.postgresql.org.br/">http://pgbr.postgresql.org.br/</a>
+</p>
+
+<p>
+PGConf.DE 2011 is the German-speaking PostgreSQL Conference and will
+take place on November 11th in the Rheinisches Industriemuseum in
+Oberhausen, Germany.  Call for Papers is open.
+<a href="http://2011.pgconf.de/">http://2011.pgconf.de/</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>
+Robert Haas pushed:
+</p>
+
+<p>
+- Add new pgbench switch, --unlogged-tables.  This entails adjusting
+  pgbench to use getopt_long() rather than getopt().
+  <a href="http://git.postgresql.org/pg/commitdiff/2d6fee09eba8474d9a69c08bf716f3e2d31e5fdf">http://git.postgresql.org/pg/commitdiff/2d6fee09eba8474d9a69c08bf716f3e2d31e5fdf</a>
+</p>
+
+<p>
+- Add new pgbench options, --tablespace and --index-tablespace.  Per a
+  request from Greg Smith.
+  <a href="http://git.postgresql.org/pg/commitdiff/7c26395661ce549621db6fa93c0abb9cdbac9837">http://git.postgresql.org/pg/commitdiff/7c26395661ce549621db6fa93c0abb9cdbac9837</a>
+</p>
+
+<p>
+- Improvements to SQL/MED documentation.  Laurenz Albe, somewhat
+  modified by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/f5af8eed9201e50bc5c761809ff57ef1ace91502">http://git.postgresql.org/pg/commitdiff/f5af8eed9201e50bc5c761809ff57ef1ace91502</a>
+</p>
+
+<p>
+- Add some environment checks prior to sepgsql regression testing.
+  This probably needs more work, but it's a start.  KaiGai Kohei
+  <a href="http://git.postgresql.org/pg/commitdiff/8cca49d8a0d969e1c0f08779e8230466e395b813">http://git.postgresql.org/pg/commitdiff/8cca49d8a0d969e1c0f08779e8230466e395b813</a>
+</p>
+
+<p>
+- Clarify which relkinds accept column comments.  Per discussion with
+  Josh Kupershmidt.
+  <a href="http://git.postgresql.org/pg/commitdiff/c80be8a816ac4bf8b910aaaec599c683804bcd77">http://git.postgresql.org/pg/commitdiff/c80be8a816ac4bf8b910aaaec599c683804bcd77</a>
+</p>
+
+<p>
+- Only display column comments for relkinds that support them.  Josh
+  Kupershmidt, with minor modifications by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/8c18f3f0e15738633231b31d8937b2710b38975f">http://git.postgresql.org/pg/commitdiff/8c18f3f0e15738633231b31d8937b2710b38975f</a>
+</p>
+
+<p>
+- Fix typo.  Noted by Josh Kupershmidt.
+  <a href="http://git.postgresql.org/pg/commitdiff/a8302803ab225e87458037b922aceee9864d9f54">http://git.postgresql.org/pg/commitdiff/a8302803ab225e87458037b922aceee9864d9f54</a>
+</p>
+
+<p>
+- Move new pgbench options to correct section of --help output.
+  <a href="http://git.postgresql.org/pg/commitdiff/60fb25a3f56bd78e961cc7263e5ae11e1eceeb5e">http://git.postgresql.org/pg/commitdiff/60fb25a3f56bd78e961cc7263e5ae11e1eceeb5e</a>
+</p>
+
+<p>
+- Reduce sinval synchronization overhead.  Testing shows that the
+  overhead of acquiring and releasing SInvalReadLock and msgNumLock on
+  high-core count boxes can waste a lot of CPU time and hurt
+  performance.  This patch adds a per-backend flag that allows us to
+  skip all that locking in most cases.  Further testing shows that
+  this improves performance even when sinval traffic is very high.
+  Patch by me.  Review and testing by Noah Misch.
+  <a href="http://git.postgresql.org/pg/commitdiff/b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4">http://git.postgresql.org/pg/commitdiff/b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Silence compiler warning about uninitialized variable.  It is set
+  correctly on the only path that uses it, but the compiler can't know
+  that.
+  <a href="http://git.postgresql.org/pg/commitdiff/74e6d37276564d4be1f60d9edb76d7d066395773">http://git.postgresql.org/pg/commitdiff/74e6d37276564d4be1f60d9edb76d7d066395773</a>
+</p>
+
+<p>
+- Don't build replacement getpeereid function on mingw.  Windows
+  doesn't have Unix sockets, so it's not needed, and moreover causes
+  compile warnings.
+  <a href="http://git.postgresql.org/pg/commitdiff/c9737310d5f9b87b5edb3674b5d34eea2f198a0b">http://git.postgresql.org/pg/commitdiff/c9737310d5f9b87b5edb3674b5d34eea2f198a0b</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Replace printf format %i by %d.  They are identical, but the
+  overwhelming majority of the code uses %d, so standardize on that.
+  <a href="http://git.postgresql.org/pg/commitdiff/ce8d7bb6440710058503d213b2aafcdf56a5b481">http://git.postgresql.org/pg/commitdiff/ce8d7bb6440710058503d213b2aafcdf56a5b481</a>
+</p>
+
+<p>
+- Add missing newlines at end of error messages
+  <a href="http://git.postgresql.org/pg/commitdiff/e67efb01e886d69d40d1cd87fba4507e8bb1035e">http://git.postgresql.org/pg/commitdiff/e67efb01e886d69d40d1cd87fba4507e8bb1035e</a>
+</p>
+
+<p>
+- Minor message style adjustment
+  <a href="http://git.postgresql.org/pg/commitdiff/0fe8150827693fca429a01b1cf2914f7f14d3b2d">http://git.postgresql.org/pg/commitdiff/0fe8150827693fca429a01b1cf2914f7f14d3b2d</a>
+</p>
+
+<p>
+- Add host name resolution information to pg_hba.conf error messages.
+  This is to be able to analyze issues with host names in pg_hba.conf.
+  <a href="http://git.postgresql.org/pg/commitdiff/8a0fa9cad9939f53f0b496d95d7e7fd9cfab0e9c">http://git.postgresql.org/pg/commitdiff/8a0fa9cad9939f53f0b496d95d7e7fd9cfab0e9c</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Check to see whether libxml2 handles error context the way we
+  expect.  It turns out to be possible to link against a libxml2.so
+  that does this differently than the version we configured and built
+  against, so we need a runtime check to avoid bizarre behavior.  Per
+  report from Bernd Helmle.  Patch by Florian Pflug.
+  <a href="http://git.postgresql.org/pg/commitdiff/c1420fcf7d9e899b3378e25f5e21776f6461b4a4">http://git.postgresql.org/pg/commitdiff/c1420fcf7d9e899b3378e25f5e21776f6461b4a4</a>
+</p>
+
+<p>
+- Fix pg_restore's direct-to-database mode for
+  standard_conforming_strings.  pg_backup_db.c contained a mini SQL
+  lexer with which it tried to identify boundaries between SQL
+  commands, but that code was not designed to cope with
+  standard_conforming_strings, and would get the wrong answer if a
+  backslash immediately precedes a closing single quote in such a
+  string, as per report from Julian Mehnle.  The bug only affects
+  direct-to-database restores from archive files made with
+  standard_conforming_strings = on.  Rather than complicating the code
+  some more to try to fix that, let's just rip it all out.  The only
+  reason it was needed was to cope with COPY data embedded into
+  ordinary archive entries, which was a layout that was used only for
+  about the first three weeks of the archive format's existence, and
+  never in any production release of pg_dump.  Instead, just rely on
+  the archive file layout to tell us whether we're printing COPY data
+  or not.  This bug represents a data corruption hazard in all
+  releases in which standard_conforming_strings can be turned on, ie
+  8.2 and later, so back-patch to all supported branches.
+  <a href="http://git.postgresql.org/pg/commitdiff/6545a901aaf84cb05212bb6a7674059908f527c3">http://git.postgresql.org/pg/commitdiff/6545a901aaf84cb05212bb6a7674059908f527c3</a>
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Fix pg_update to properly test for the data directory's existence on
+  Win32.  Backpatch to 9.1.
+  <a href="http://git.postgresql.org/pg/commitdiff/a31dc392d684627d0943fe67491bea91c5e619aa">http://git.postgresql.org/pg/commitdiff/a31dc392d684627d0943fe67491bea91c5e619aa</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Timothy D. F. Lewis sent in another revision of a patch which allows
+people to set the maximum number of large objects which can be
+vacuumed.
+</p>
+
+<p>
+Alexey Klyukin sent in another revision of the patch intended to
+validate configuration files.
+</p>
+
+<p>
+Jeff Janes sent in a patch to allow running pgbench in
+single-transaction mode.
+</p>
+
+<p>
+Florian Pflug sent in another revision of a patch intended to fix a
+failure mode in XML.
+</p>
+
+<p>
+Heikki Linnakangas sent in another revision of the patch to build GiST
+indexes faster.
+</p>
+
+<p>
+Josh Kupershmidt sent in another revision of the patch to display
+object comments in psql.
+</p>
+
+<p>
+Aron Wieck sent in another revision of the vacuumlo patch.
+</p>
+
+<p>
+Pavel Stehule sent in another revision of the patch to enhance error
+reporting.
+</p>
+
+<p>
+Alvaro Herrera sent in another revision of the FOR KEY LOCK patch.
+</p>
+
+<p>
+Robert Haas sent in another revision of the patch intended to reduce
+the number of sinval calls.
+</p>
+
+<p>
+Nikhil Sontakke sent in two revisions of a patch to allow CHECK
+constraints to be only on parent tables in an inheritance (partition)
+hierarchy.
+</p>
+
+<p>
+Alvaro Herrera sent in another revision of the patch to catalog NOT
+NULL constraints.
+</p>
+
+<p>
+Peter Geoghegan sent in another revision of the patch intended to
+reduce power consumption when idle.
+</p>
+
+<p>
+Andrew Dunstan sent in a patch to clean up PL/PythonU.
+</p>
+
+<p>
+Shigeru HANADA sent in another revision of the patch to add per-column
+options to foreign data wrappers.
+</p>
+
+<p>
+Robert Haas sent in two revisions of a patch intended to reduce
+internal contention in pgbench.
+
+</p>
+
-- 
2.39.5