From dfd34f439817ed6f061ff56eb6d869ff739bd21e Mon Sep 17 00:00:00 2001
From: David Fetter <david@fetter.org>
Date: Mon, 6 Jun 2011 05:11:16 +0000
Subject: [PATCH] PostgreSQL Weekly News June 05, 2011

git-svn-id: file:///Users/dpage/pgweb/svn-repo/trunk@2857 8f5c7a92-453e-0410-a47f-ad33c8a6b003
---
 portal/files/weeklynews.xml                   |  26 +-
 portal/template/en/community/weeklynews.html  |   1 +
 .../en/community/weeklynews/pwn20110605.html  | 598 ++++++++++++++++++
 3 files changed, 612 insertions(+), 13 deletions(-)
 create mode 100644 portal/template/en/community/weeklynews/pwn20110605.html

diff --git a/portal/files/weeklynews.xml b/portal/files/weeklynews.xml
index 916cb06f..0df9bbb6 100644
--- a/portal/files/weeklynews.xml
+++ b/portal/files/weeklynews.xml
@@ -10,6 +10,19 @@
 <description></description>
 <language>en</language>
 
+<item>
+<title>PostgreSQL Weekly News June 5th 2011</title>
+<description>
+The Austin Texas PUG is meeting on Wednesday, June 8th at 6:30pm.
+Pizza will be available to people who R, SVP, to
+austinpug AT postgresql DOT org.  Details below.
+&#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/pwn20110605</guid>
+<pubDate>Sun, 05 Jun 2011 00:00:00 PST</pubDate>
+</item>
 <item>
 <title>PostgreSQL Weekly News May 29th 2011</title>
 <description>
@@ -113,18 +126,5 @@ This is the (latest ;) last planned alpha for 9.1.  You can get it here:
 <guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110403</guid>
 <pubDate>Sun, 03 Apr 2011 00:00:00 PST</pubDate>
 </item>
-<item>
-<title>PostgreSQL Weekly News April 1st 2011</title>
-<description>
-Long-time contributor Julian Assange, using a sophisticated regular
-expression utility on the PostgreSQL source code, found multiple back
-doors for the US National Security Agency created by newer contributor
-Tom Lane.  As a result, Mr. Lane has been dismissed from the project.
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20110401</guid>
-<pubDate>Fri, 01 Apr 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 9af0c365..95c1f116 100644
--- a/portal/template/en/community/weeklynews.html
+++ b/portal/template/en/community/weeklynews.html
@@ -11,6 +11,7 @@ Weekly News
 <p>Here is the <a href="http://www.postgresql.org/files/weeklynews.xml">RSS feed</a>.</p>
 
 <ul>
+    <li><a href="/community/weeklynews/pwn20110605">June 5th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110529">May 29th 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110522">May 22nd 2011</a></li>
     <li><a href="/community/weeklynews/pwn20110515">May 15th 2011</a></li>
diff --git a/portal/template/en/community/weeklynews/pwn20110605.html b/portal/template/en/community/weeklynews/pwn20110605.html
new file mode 100644
index 00000000..98c26f6f
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20110605.html
@@ -0,0 +1,598 @@
+<!-- BEGIN page_title_block -->
+Weekly News - June 05 2011
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - June 05 2011</h1>
+
+<p>
+The Austin Texas PUG is meeting on Wednesday, June 8th at 6:30pm.
+Pizza will be available to people who R, SVP, to
+austinpug AT postgresql DOT org.  Details below.
+<a href="http://pugs.postgresql.org/austinpug">http://pugs.postgresql.org/austinpug</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 Product News</h2>
+<p>
+devart dotConnect for PostgreSQL, an ADO.NET provider, released.
+<a href="http://www.devart.com/dotconnect/postgresql/">http://www.devart.com/dotconnect/postgresql/</a>
+</p>
+
+<p>
+MyJSQLView 3.29, a GUI tool that can be used with PostgreSQL, released.
+<a href="http://dandymadeproductions.com/projects/MyJSQLView/index.html">http://dandymadeproductions.com/projects/MyJSQLView/index.html</a>
+</p>
+
+<p>
+PostgreDAC 2.6.3, a Delphi/C++ builder for PostgreSQL, released.
+<a href="http://microolap.com/products/connectivity/postgresdac/download/">http://microolap.com/products/connectivity/postgresdac/download/</a>
+</p>
+
+<p>
+Slony-ctl 1.2.0, a set of scripts for creating and managing Slony
+clusters, released.
+<a href="http://pgfoundry.org/projects/slony1-ctl/">http://pgfoundry.org/projects/slony1-ctl/</a>
+</p>
+
+<h2>PostgreSQL Jobs for June</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2011-06/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-06/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+PG Session 2, on PostGIS, will be held on June 23rd in Paris.  The CfP
+is open!
+<a href="http://www.postgresql-sessions.org/en/2/">http://www.postgresql-sessions.org/en/2/</a>
+</p>
+
+<p>
+CHAR(11), the PostgreSQL Conference on Clustering, High Availability
+and Replication is now open for online registration and bookings.
+July 11-12 2011 in Cambridge, UK.
+<a href="http://www.char11.org/">http://www.char11.org/</a>
+</p>
+
+<p>
+PostgreSQL Conference China 2011 will be held in Guangzhou July
+15-16, 2011.
+<a href="http://wiki.postgresql.org/wiki/Pgconchina2011">http://wiki.postgresql.org/wiki/Pgconchina2011</a>
+</p>
+
+<p>
+PDXPUG is hosting PgDay on Sunday, July 24, 2011, one day before
+OSCON, in Portland, Oregon, USA.  Details here:
+<a href="http://pugs.postgresql.org/node/1663">http://pugs.postgresql.org/node/1663</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>
+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>
+
+<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>
+Alvaro Herrera pushed:
+</p>
+
+<p>
+- Make message more consistent
+  <a href="http://git.postgresql.org/pg/commitdiff/5177dfefc532ea481bf70d1bb8a493f835a9c57c">http://git.postgresql.org/pg/commitdiff/5177dfefc532ea481bf70d1bb8a493f835a9c57c</a>
+</p>
+
+<p>
+- Remove usage of &PL_sv_undef in hashes and arrays.  According to
+  perlguts, &PL_sv_undef is not the right thing to use in those cases
+  because it doesn't behave the same way as an undef value via Perl
+  code.  Seems the intuitive way to deal with undef values is subtly
+  enough broken that it's hard to notice when misused.  The broken
+  uses got inadvertently introduced in commit
+  87bb2ade2ce646083f39d5ab3e3307490211ad04 by Alexey Klyukin, Alex
+  Hunsaker and myself on 2011-02-17; no backpatch is necessary.  Per
+  testing report from Greg Mullane.  Author: Alex Hunsaker
+  <a href="http://git.postgresql.org/pg/commitdiff/7de38741c0438cdece0e22699de8ffd5797735fb">http://git.postgresql.org/pg/commitdiff/7de38741c0438cdece0e22699de8ffd5797735fb</a>
+</p>
+
+<p>
+- Fix pg_get_constraintdef to cope with NOT VALID constraints.  This
+  case was missed when NOT VALID constraints were first introduced in
+  commit 722bf7017bbe796decc79c1fde03e7a83dae9ada by Simon Riggs on
+  2011-02-08.  Among other things, it causes pg_dump to omit the NOT
+  VALID flag when dumping such constraints, which may cause them to
+  fail to load afterwards, if they contained values failing the
+  constraint.  Per report from Thom Brown.
+  <a href="http://git.postgresql.org/pg/commitdiff/048417511aef8d5fb2d541b17b73afc730935cd5">http://git.postgresql.org/pg/commitdiff/048417511aef8d5fb2d541b17b73afc730935cd5</a>
+</p>
+
+<p>
+Heikki Linnakangas pushed:
+</p>
+
+<p>
+- The row-version chaining in Serializable Snapshot Isolation was
+  still wrong.  On further analysis, it turns out that it is not
+  needed to duplicate predicate locks to the new row version at
+  update, the lock on the version that the transaction saw as visible
+  is enough.  However, there was a different bug in the code that
+  checks for dangerous structures when a new rw-conflict happens.  Fix
+  that bug, and remove all the row-version chaining related code.
+  Kevin Grittner & Dan Ports, with some comment editorialization by
+  me.
+  <a href="http://git.postgresql.org/pg/commitdiff/3103f9a77d005f9d8b8ef492298bbbbf6c4b843f">http://git.postgresql.org/pg/commitdiff/3103f9a77d005f9d8b8ef492298bbbbf6c4b843f</a>
+</p>
+
+<p>
+- SSI comment fixes and enhancements.  Notably, document that the
+  conflict-out flag actually means that the transaction has a conflict
+  out to a transaction that committed before the flagged transaction.
+  Kevin Grittner
+  <a href="http://git.postgresql.org/pg/commitdiff/c8630919e08c2e91435807caecb4b44c7722bf9e">http://git.postgresql.org/pg/commitdiff/c8630919e08c2e91435807caecb4b44c7722bf9e</a>
+</p>
+
+<p>
+Magnus Hagander pushed:
+</p>
+
+<p>
+- Don't include local line on platforms without support.  Since we now
+  include a sample line for replication on local connections in
+  pg_hba.conf, don't include it where local connections aren't
+  available (such as on win32).  Also make sure we use authmethodlocal
+  and not authmethod on the sample line.
+  <a href="http://git.postgresql.org/pg/commitdiff/764bde0f1641cc3aafa2c221c56bd3a8129d9e3b">http://git.postgresql.org/pg/commitdiff/764bde0f1641cc3aafa2c221c56bd3a8129d9e3b</a>
+</p>
+
+<p>
+- Refuse "local" lines in pg_hba.conf on platforms that don't support
+  it.  This makes the behavior compatible with that of hostssl, which
+  also throws an error when there is no SSL support included.
+  <a href="http://git.postgresql.org/pg/commitdiff/5830f69665053f78cfd31e39f40bb23ad91748a8">http://git.postgresql.org/pg/commitdiff/5830f69665053f78cfd31e39f40bb23ad91748a8</a>
+</p>
+
+<p>
+- Don't recommend upgrading to latest available Windows SDK.  We only
+  support up to version 7.0, so don't recommend upgrading past it.
+  The rest of the documentation around this was already updated, but
+  one spot was missed.
+  <a href="http://git.postgresql.org/pg/commitdiff/2367da886d4ab903c7bf5037b363ca10489cdf85">http://git.postgresql.org/pg/commitdiff/2367da886d4ab903c7bf5037b363ca10489cdf85</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Suppress foreign data wrappers and foreign servers in partial dumps.
+  This is consistent with the behavior of other global objects such as
+  languages and extensions.  Omitting foreign servers also omits the
+  respective user mappings.
+  <a href="http://git.postgresql.org/pg/commitdiff/3001b76308e9189ff471c54b1823621e03dc1359">http://git.postgresql.org/pg/commitdiff/3001b76308e9189ff471c54b1823621e03dc1359</a>
+</p>
+
+<p>
+- Recode non-ASCII characters in source to UTF-8.  For consistency,
+  have all non-ASCII characters from contributors' names in the source
+  be in UTF-8.  But remove some other more gratuitous uses of
+  non-ASCII characters.
+  <a href="http://git.postgresql.org/pg/commitdiff/ba4cacf0756f71e175d25bac78834715a353e64e">http://git.postgresql.org/pg/commitdiff/ba4cacf0756f71e175d25bac78834715a353e64e</a>
+</p>
+
+<p>
+- Use entities to encode non-ASCII characters in SGML documentation.
+  This has already been the case for the most part; just some cases
+  had slipped through.
+  <a href="http://git.postgresql.org/pg/commitdiff/85ffed431ae6fff0d5fbafd9a48b330542f2f4d9">http://git.postgresql.org/pg/commitdiff/85ffed431ae6fff0d5fbafd9a48b330542f2f4d9</a>
+</p>
+
+<p>
+- Some copy editing of the release notes
+  <a href="http://git.postgresql.org/pg/commitdiff/596b0c213f2f7ffa72d0d5b68e1da91c366dc72b">http://git.postgresql.org/pg/commitdiff/596b0c213f2f7ffa72d0d5b68e1da91c366dc72b</a>
+</p>
+
+<p>
+- Sort COMMENT synopsis and add more examples.  Josh Kupershmidt
+  <a href="http://git.postgresql.org/pg/commitdiff/c82d415acc39bc30962e692229c04ee23dae27b7">http://git.postgresql.org/pg/commitdiff/c82d415acc39bc30962e692229c04ee23dae27b7</a>
+</p>
+
+<p>
+- Truncate id to <=44 characters.  This is the original DocBook SGML
+  limit, but apparently most installations have changed it or ignore
+  it, which is why few people have run into this problem.  pointed out
+  by Brendan Jurd
+  <a href="http://git.postgresql.org/pg/commitdiff/3ece3913d056245d78450793fc5ad18e229a3948">http://git.postgresql.org/pg/commitdiff/3ece3913d056245d78450793fc5ad18e229a3948</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Fix VACUUM so that it always updates pg_class.reltuples/relpages.
+  When we added the ability for vacuum to skip heap pages by
+  consulting the visibility map, we made it just not update the
+  reltuples/relpages statistics if it skipped any pages.  But this
+  could leave us with extremely out-of-date stats for a table that
+  contains any unchanging areas, especially for TOAST tables which
+  never get processed by ANALYZE.  In particular this could result in
+  autovacuum making poor decisions about when to process the table, as
+  in recent report from Florian Helmberger.  And in general it's a bad
+  idea to not update the stats at all.  Instead, use the previous
+  values of reltuples/relpages as an estimate of the tuple density in
+  unvisited pages.  This approach results in a "moving average"
+  estimate of reltuples, which should converge to the correct value
+  over multiple VACUUM and ANALYZE cycles even when individual
+  measurements aren't very good.  This new method for updating
+  reltuples is used by both VACUUM and ANALYZE, with the result that
+  we no longer need the grotty interconnections that caused ANALYZE to
+  not update the stats depending on what had happened in the parent
+  VACUUM command.  Also, fix the logic for skipping all-visible pages
+  during VACUUM so that it looks ahead rather than behind to decide
+  what to do, as per a suggestion from Greg Stark.  This eliminates
+  useless scanning of all-visible pages at the start of the relation
+  or just after a not-all-visible page.  In particular, the first few
+  pages of the relation will not be invariably included in the scanned
+  pages, which seems to help in not overweighting them in the
+  reltuples estimate.  Back-patch to 8.4, where the visibility map was
+  introduced.
+  <a href="http://git.postgresql.org/pg/commitdiff/b4b6923e03f4d29636a94f6f4cc2f5cf6298b8c8">http://git.postgresql.org/pg/commitdiff/b4b6923e03f4d29636a94f6f4cc2f5cf6298b8c8</a>
+</p>
+
+<p>
+- Fix portability bugs in use of credentials control messages for peer
+  auth.  Even though our existing code for handling credentials
+  control messages has been basically unchanged since 2001, it was
+  fundamentally wrong: it did not ensure proper alignment of the
+  supplied buffer, and it was calculating buffer sizes and message
+  sizes incorrectly.  This led to failures on platforms where
+  alignment padding is relevant, for instance FreeBSD on 64-bit
+  platforms, as seen in a recent Debian bug report passed on by Martin
+  Pitt (<a href="http://bugs.debian.org//cgi-bin/bugreport.cgi?bug=612888).">http://bugs.debian.org//cgi-bin/bugreport.cgi?bug=612888).</a>
+  Rewrite to do the message-whacking using the macros specified in RFC
+  2292, following a suggestion from Theo de Raadt in that thread.
+  Tested by me on Debian/kFreeBSD-amd64; since OpenBSD and NetBSD
+  document the identical CMSG API, it should work there too.
+  Back-patch to all supported branches.
+  <a href="http://git.postgresql.org/pg/commitdiff/13c00ae8c73ee9635c11059925814b351dc3593c">http://git.postgresql.org/pg/commitdiff/13c00ae8c73ee9635c11059925814b351dc3593c</a>
+</p>
+
+<p>
+- Replace use of credential control messages with
+  getsockopt(LOCAL_PEERCRED).  It turns out the reason we hadn't found
+  out about the portability issues with our credential-control-message
+  code is that almost no modern platforms use that code at all; the
+  ones that used to need it now offer getpeereid(), which we choose
+  first.  The last holdout was NetBSD, and they added getpeereid() as
+  of 5.0.  So far as I can tell, the only live platform on which that
+  code was being exercised was Debian/kFreeBSD, ie, FreeBSD kernel
+  with Linux userland --- since glibc doesn't provide getpeereid(), we
+  fell back to the control message code.  However, the FreeBSD kernel
+  provides a LOCAL_PEERCRED socket parameter that's functionally
+  equivalent to Linux's SO_PEERCRED.  That is both much simpler to use
+  than control messages, and superior because it doesn't require
+  receiving a message from the other end at just the right time.
+  Therefore, add code to use LOCAL_PEERCRED when necessary, and rip
+  out all the credential-control-message code in the backend.  (libpq
+  still has such code so that it can still talk to pre-9.1 servers ...
+  but eventually we can get rid of it there too.)  Clean up related
+  autoconf probes, too.  This means that libpq's requirepeer parameter
+  now works on exactly the same platforms where the backend supports
+  peer authentication, so adjust the documentation accordingly.
+  <a href="http://git.postgresql.org/pg/commitdiff/be4585b1c27ac5dbdd0d61740d18f7ad9a00e268">http://git.postgresql.org/pg/commitdiff/be4585b1c27ac5dbdd0d61740d18f7ad9a00e268</a>
+</p>
+
+<p>
+- Protect GIST logic that assumes penalty values can't be negative.
+  Apparently sane-looking penalty code might return small negative
+  values, for example because of roundoff error.  This will confuse
+  places like gistchoose().  Prevent problems by clamping negative
+  penalty values to zero.  (Just to be really sure, I also made it
+  force NaNs to zero.) Back-patch to all supported branches.
+  Alexander Korotkov
+  <a href="http://git.postgresql.org/pg/commitdiff/6923d699bc3c46ca2c5d8c12fe1c5c39ecfee11d">http://git.postgresql.org/pg/commitdiff/6923d699bc3c46ca2c5d8c12fe1c5c39ecfee11d</a>
+</p>
+
+<p>
+- Further improvements in pg_ctl's new wait-for-postmaster-start
+  logic.  Add a postmaster_is_alive() test to the wait loop, so that
+  we stop waiting if the postmaster dies without removing its pidfile.
+  Unfortunately this only helps after the postmaster has created its
+  pidfile, since until then we don't know which PID to check.  But if
+  it never does create the pidfile, we can give up in a relatively
+  short time, so this is a useful addition in practice.  Per
+  suggestion from Fujii Masao, though this doesn't look very much like
+  his patch.  In addition, improve pg_ctl's ability to cope with
+  pre-existing pidfiles.  Such a file might or might not represent a
+  live postmaster that is going to block our postmaster from starting,
+  but the previous code pre-judged the situation and gave up waiting
+  immediately.  Now, we will wait for up to 5 seconds to see if our
+  postmaster overwrites such a file.  This issue interacts with
+  Fujii's patch because we would make the wrong conclusion if we did
+  the postmaster_is_alive() test with a pre-existing PID.  All of this
+  could be improved if we rewrote start_postmaster() so that it could
+  report the child postmaster's PID, so that we'd know a-priori the
+  correct PID to test with postmaster_is_alive().  That looks like a
+  bit too much change for so late in the 9.1 development cycle,
+  unfortunately.
+  <a href="http://git.postgresql.org/pg/commitdiff/3c485ca8e6580409284ac50623286b0fb8cd4a57">http://git.postgresql.org/pg/commitdiff/3c485ca8e6580409284ac50623286b0fb8cd4a57</a>
+</p>
+
+<p>
+- Allow hash joins to be interrupted while searching hash table for
+  match.  Per experimentation with a recent example, in which
+  unreasonable amounts of time could elapse before the backend would
+  respond to a query-cancel.  This might be something to back-patch,
+  but the patch doesn't apply cleanly because this code was rewritten
+  for 9.1.  Given the lack of field complaints I won't bother for now.
+  Cédric Villemain
+  <a href="http://git.postgresql.org/pg/commitdiff/0c99d41ec887051fb0cc6e35e358ecc936a13584">http://git.postgresql.org/pg/commitdiff/0c99d41ec887051fb0cc6e35e358ecc936a13584</a>
+</p>
+
+<p>
+- Implement getpeereid() as a src/port compatibility function.  This
+  unifies a bunch of ugly #ifdef's in one place.  Per discussion, we
+  only need this where HAVE_UNIX_SOCKETS, so no need to cover Windows.
+  Marko Kreen, some adjustment by Tom Lane
+  <a href="http://git.postgresql.org/pg/commitdiff/3980f7fc6ecb75952ebe76c3d30ec6731728098d">http://git.postgresql.org/pg/commitdiff/3980f7fc6ecb75952ebe76c3d30ec6731728098d</a>
+</p>
+
+<p>
+- Typo fix.
+  <a href="http://git.postgresql.org/pg/commitdiff/dd2ddfb1cd40393731637101c713a3446cf92144">http://git.postgresql.org/pg/commitdiff/dd2ddfb1cd40393731637101c713a3446cf92144</a>
+</p>
+
+<p>
+- Disallow SELECT FOR UPDATE/SHARE on sequences.  We can't allow this
+  because such an operation stores its transaction XID into the
+  sequence tuple's xmax.  Because VACUUM doesn't process sequences
+  (and we don't want it to start doing so), such an xmax value won't
+  get frozen, meaning it will eventually refer to nonexistent pg_clog
+  storage, and even wrap around completely.  Since the row lock is
+  ignored by nextval and setval, the usefulness of the operation is
+  highly debatable anyway.  Per reports of trouble with pgpool 3.0,
+  which had ill-advisedly started using such commands as a form of
+  locking.  In HEAD, also disallow SELECT FOR UPDATE/SHARE on toast
+  tables.  Although this does work safely given the current
+  implementation, there seems no good reason to allow it.  I refrained
+  from changing that behavior in back branches, however.
+  <a href="http://git.postgresql.org/pg/commitdiff/21538377ee6a0ee91f756726bd8b3de6d19fd20a">http://git.postgresql.org/pg/commitdiff/21538377ee6a0ee91f756726bd8b3de6d19fd20a</a>
+</p>
+
+<p>
+- Clean up after erroneous SELECT FOR UPDATE/SHARE on a sequence.  My
+  previous commit disallowed this operation, but did nothing about
+  cleaning up the damage if one had already been done.  With the
+  operation disallowed, it's okay to just forcibly clear xmax in a
+  sequence's tuple, since any value seen there could not represent a
+  live transaction's lock.  So, any sequence-specific operation will
+  repair the problem automatically, whether or not the user has
+  already seen "could not access status of transaction" failures.
+  <a href="http://git.postgresql.org/pg/commitdiff/ea6eda64a6425923463d358e2915980e81280483">http://git.postgresql.org/pg/commitdiff/ea6eda64a6425923463d358e2915980e81280483</a>
+</p>
+
+<p>
+- libpq needs its own copy of src/port/getpeereid ... on some
+  platforms, anyway.  Per buildfarm.
+  <a href="http://git.postgresql.org/pg/commitdiff/2021c5a53a9dd7bb181b67475c960ae730f3a4fc">http://git.postgresql.org/pg/commitdiff/2021c5a53a9dd7bb181b67475c960ae730f3a4fc</a>
+</p>
+
+<p>
+- Looks like we can't declare getpeereid on Windows anyway ... for
+  lack of the uid_t and gid_t typedefs.  Per buildfarm.
+  <a href="http://git.postgresql.org/pg/commitdiff/680ea6a6df345218f655eaad2c25f98900487438">http://git.postgresql.org/pg/commitdiff/680ea6a6df345218f655eaad2c25f98900487438</a>
+</p>
+
+<p>
+- Handle domains when checking for recursive inclusion of composite
+  types.  We need this now because we allow domains over arrays, and
+  we'll probably allow domains over composites pretty soon, which
+  makes the problem even more obvious.  Although domains over arrays
+  also exist in previous versions, this does not need to be
+  back-patched, because the coding used in older versions successfully
+  "looked through" domains over arrays.  The problem is exposed by not
+  treating a domain as having a typelem.  Problem identified by Noah
+  Misch, though I did not use his patch, since it would require
+  additional work to handle domains over composites that way.  This
+  approach is more future-proof.
+  <a href="http://git.postgresql.org/pg/commitdiff/aff97b1f4e3630069a370be663b847c777b58319">http://git.postgresql.org/pg/commitdiff/aff97b1f4e3630069a370be663b847c777b58319</a>
+</p>
+
+<p>
+- Need to list getpeereid.c in .gitignore, too ...
+  <a href="http://git.postgresql.org/pg/commitdiff/52caa355ee6fd34670b6387e14c821d9128e5c88">http://git.postgresql.org/pg/commitdiff/52caa355ee6fd34670b6387e14c821d9128e5c88</a>
+</p>
+
+<p>
+- Fix failure to check whether a rowtype's component types are
+  sortable.  The existence of a btree opclass accepting composite
+  types caused us to assume that every composite type is sortable.
+  This isn't true of course; we need to check if the column types are
+  all sortable.  There was logic for this for the case of array
+  comparison (ie, check that the element type is sortable), but we
+  missed the point for rowtypes.  Per Teodor's report of an ANALYZE
+  failure for an unsortable composite type.  Rather than just add some
+  more ad-hoc logic for this, I moved knowledge of the issue into
+  typcache.c.  The typcache will now only report out array_eq,
+  record_cmp, and friends as usable operators if the array or
+  composite type will work with those functions.  Unfortunately we
+  don't have enough info to do this for anonymous RECORD types; in
+  that case, just assume it will work, and take the runtime failure as
+  before if it doesn't.  This patch might be a candidate for
+  back-patching at some point, but given the lack of complaints from
+  the field, I'd rather just test it in HEAD for now.  Note: most of
+  the places touched in this patch will need further work when we get
+  around to supporting hashing of record types.
+  <a href="http://git.postgresql.org/pg/commitdiff/ea8e42f3a0848f506d8a1b9c74967248005291cd">http://git.postgresql.org/pg/commitdiff/ea8e42f3a0848f506d8a1b9c74967248005291cd</a>
+</p>
+
+<p>
+- Reset reindex-in-progress state before reverifying an exclusion
+  constraint.  This avoids an Assert failure when we try to use
+  ordinary index fetches while checking for exclusion conflicts.  Per
+  report from Noah Misch.  No need for back-patch because the Assert
+  wasn't there before 9.1.
+  <a href="http://git.postgresql.org/pg/commitdiff/dccfb72892acabd25568539ec882cc44c57c25bd">http://git.postgresql.org/pg/commitdiff/dccfb72892acabd25568539ec882cc44c57c25bd</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Avoid creating init fork for unlogged indexes when it already
+  exists.  Report by Greg Sabino Mullane, diagnosis and preliminary
+  patch by Andres Freund, corrections by me.
+  <a href="http://git.postgresql.org/pg/commitdiff/b8be5431a2baa2ea4a5140f1a49c3360deb4d64e">http://git.postgresql.org/pg/commitdiff/b8be5431a2baa2ea4a5140f1a49c3360deb4d64e</a>
+</p>
+
+<p>
+- Fix vim-induced typo.
+  <a href="http://git.postgresql.org/pg/commitdiff/5295fa8c0bb396bf2866205e093bc04d7a3394fe">http://git.postgresql.org/pg/commitdiff/5295fa8c0bb396bf2866205e093bc04d7a3394fe</a>
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Use proper SGML doc entities rather than angle-brackets.  Marco
+  Nenciarini
+  <a href="http://git.postgresql.org/pg/commitdiff/a20bc9c8666ad81ff3fe26cfab2efd42d6df7f34">http://git.postgresql.org/pg/commitdiff/a20bc9c8666ad81ff3fe26cfab2efd42d6df7f34</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Magnus Hagander sent in a patch to fix an infelicity in SSL handling
+in pg_hba.conf.
+</p>
+
+<p>
+Florian Pflug sent in two revisions of a patch to fix a bug in XPATH()
+when the expression returns a scalar value.
+</p>
+
+<p>
+Heikki Linnakangas sent in a patch to fix an issue with SSI predicate
+locking, changing from row to tuple.
+</p>
+
+<p>
+Heikki Linnakangas sent in two revisions of a patch to fix some
+infelicities in nested CASE-WHEN scoping.
+</p>
+
+<p>
+Alvaro Herrera sent in four revisions of a patch to enable CHECK
+constraints to be declared as NOT VALID, as FOREIGN KEY ones can now.
+</p>
+
+<p>
+Radoslaw Smogura sent in a patch to create BLOBs and attendant
+structures.
+</p>
+
+<p>
+Mark Kirkwood sent in three revisions of a patch to add the ability to
+constrain backend temporary file space.
+</p>
+
+<p>
+Kevin Grittner sent in a patch to fix some comments in the SSI code.
+</p>
+
+<p>
+Teodor Sigaev and Tom Lane traded patches to fix an issue with VACUUM
+and composite row types.
+</p>
+
+<p>
+Robert Haas sent in two revisions of a patch to clean up
+InitProcLocal.
+</p>
+
+<p>
+Pavel Stehule sent in another revision of the patch to enhance GET
+DIAGNOSTICS.
+</p>
+
+<p>
+Andrew Chernow sent in two revisions of a patch to fix an issue in
+PQsetvalue.
+</p>
+
+<p>
+Kevin Grittner sent in two revisions of a patch to fix an infelicity
+in DDL under SSI.
+</p>
+
+<p>
+Alexander Korotkov sent in a WIP patch to do a faster GiST index build.
+</p>
+
+<p>
+Robert Haas sent in a WIP patch to reduce the overhead of frequent
+table locks.
+</p>
+
+<p>
+Gurjeet Singh sent in two more revisions of a patch to allow psql to
+include files relative to the current file.
+</p>
+
+<p>
+Josh Kupershmidt sent in another revision of the patch to allow \dd to
+show constraint comments in psql.
+</p>
+
+<p>
+Pavel Stehule sent in a WIP patch to add some new diagnostics to
+errors.
+
+</p>
+
-- 
2.39.5