From: David Fetter <david@fetter.org>
Date: Mon, 1 Nov 2010 05:44:34 +0000 (+0000)
Subject: PostgreSQL Weekly News October 31, 2010
X-Git-Url: http://git.postgresql.org/gitweb/static/%7B%7Bpguslink%28?a=commitdiff_plain;h=95fd08d3161650a513cc6652008beae42beb018f;p=pgweb-old.git

PostgreSQL Weekly News October 31, 2010

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

diff --git a/portal/files/weeklynews.xml b/portal/files/weeklynews.xml
index 0e31e2b2..84614958 100644
--- a/portal/files/weeklynews.xml
+++ b/portal/files/weeklynews.xml
@@ -10,6 +10,17 @@
 <description></description>
 <language>en</language>
 
+<item>
+<title>PostgreSQL Weekly News October 31st 2010</title>
+<description>
+Happy Hallowe&#x27;en/All Hallows Eve/Samhain from the PostgreSQL Weekly
+News!
+
+
+</description>
+<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20101031</guid>
+<pubDate>Sun, 31 Oct 2010 00:00:00 PST</pubDate>
+</item>
 <item>
 <title>PostgreSQL Weekly News October 24th 2010</title>
 <description>
@@ -116,17 +127,5 @@ PostgreSQL 9.0 RC1 out soon.  The more you test, the sooner 9.0.0 comes out!
 <guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20100829</guid>
 <pubDate>Sun, 29 Aug 2010 00:00:00 PST</pubDate>
 </item>
-<item>
-<title>PostgreSQL Weekly News August 22nd 2010</title>
-<description>
-Call for Papers for PGDay.EU 2010 held on December 6-8 in Stuttgart,
-Germany is open.
-&#x3C;a href=&#x22;http://2010.pgday.eu/callforpapers&#x22;&#x3E;http://2010.pgday.eu/callforpapers&#x3C;/a&#x3E;
-
-
-</description>
-<guid isPermaLink="true">http://www.postgresql.org/community/weeklynews/pwn20100822</guid>
-<pubDate>Sun, 22 Aug 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 a89e93b9..3f42b320 100644
--- a/portal/template/en/community/weeklynews.html
+++ b/portal/template/en/community/weeklynews.html
@@ -9,6 +9,7 @@ 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/pwn20101031">October 31st 2010</a></li>
     <li><a href="/community/weeklynews/pwn20101024">October 24th 2010</a></li>
     <li><a href="/community/weeklynews/pwn20101017">October 17th 2010</a></li>
     <li><a href="/community/weeklynews/pwn20101010">October 10th 2010</a></li>
diff --git a/portal/template/en/community/weeklynews/pwn20101031.html b/portal/template/en/community/weeklynews/pwn20101031.html
new file mode 100644
index 00000000..636fb7a1
--- /dev/null
+++ b/portal/template/en/community/weeklynews/pwn20101031.html
@@ -0,0 +1,523 @@
+<!-- BEGIN page_title_block -->
+Weekly News - October 31 2010
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - October 31 2010</h1>
+
+<p>
+Happy Hallowe'en/All Hallows Eve/Samhain from the PostgreSQL Weekly
+News!
+</p>
+
+<p>
+PGDay is scheduled at this year's Southern California Linux Exposition
+(SCALE) held in the LAX Hilton Hotel in the city of Los Angeles,
+California, on Friday February 25th, 2010.  Post your talk submission
+to pgday-submissions AT googlegroups DOT com.
+</p>
+
+<p>
+Andreas Scherbaum did a talk in German on PostgreSQL.  Podcast is at
+<a href="http://andreas.scherbaum.la/blog/archives/743-POFACS-PostgreSQL.html">http://andreas.scherbaum.la/blog/archives/743-POFACS-PostgreSQL.html</a>
+</p>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+psqlODBC 09.00.0200, an ODBC driver for PostgreSQL, released.
+<a href="http://psqlodbc.projects.postgresql.org/release.html">http://psqlodbc.projects.postgresql.org/release.html</a>
+</p>
+
+<p>
+Postgres-XC 0.9.3, a clustering system for PostgreSQL, released.
+<a href="http://postgres-xc.sourceforge.net/">http://postgres-xc.sourceforge.net/</a>
+</p>
+
+<h2>PostgreSQL Jobs for October</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2010-10/threads.php">http://archives.postgresql.org/pgsql-jobs/2010-10/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+The German PostgreSQL User Group is running a booth at OpenRheinRuhr
+2010 on november 13rd and 14th in Oberhausen, Germany.  Andreas
+Scherbaum is giving a talk about new features in PostgreSQL 9.0.
+<a href="http://andreas.scherbaum.la/blog/archives/744-PostgreSQL-OpenRheinRuhr-2010.html">http://andreas.scherbaum.la/blog/archives/744-PostgreSQL-OpenRheinRuhr-2010.html</a>
+</p>
+
+<p>
+The German PostgreSQL User Group is present with a booth, a talk and a
+workshop at Brandenburger Linux-Infotag 2010 in Potsdam, Germany on
+November 6th.
+<a href="http://andreas.scherbaum.la/blog/archives/746-PostgreSQL-Brandenburger-Linux-Infotag-2010.html">http://andreas.scherbaum.la/blog/archives/746-PostgreSQL-Brandenburger-Linux-Infotag-2010.html</a>
+</p>
+
+<p>
+Registration for PGDay.EU 2010 held on December 6-8 in Stuttgart,
+Germany is open.
+<a href="http://2010.pgday.eu/register">http://2010.pgday.eu/register</a>
+</p>
+
+<p>
+PgDay.IT 2010 will be in Rome this year December 10th.  The Call for
+Papers is now open.
+<a href="http://www.pgday.it/">http://www.pgday.it/</a>
+</p>
+
+<p>
+
+== PostgreSQL in the News ==
+</p>
+
+<p>
+Planet PostgreSQL: <a href="http://planet.postgresql.org/">http://planet.postgresql.org/</a>
+</p>
+
+<p>
+PostgreSQL Weekly News is brought to you this week by David Fetter
+</p>
+
+<p>
+Submit news and announcements by Sunday at 3:00pm Pacific time.
+Please send English language ones to david@fetter.org, German language
+to pwn@pgug.de, Italian language to pwn@itpug.org.  Spanish language
+to pwn@arpug.com.ar.
+</p>
+
+<h2>Reviews</h2>
+<h2>Applied Patches</h2>
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Work around rounding misbehavior exposed by buildfarm.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4ba61a487e39eaf859cd9face9520b30127e6a91">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4ba61a487e39eaf859cd9face9520b30127e6a91</a>
+</p>
+
+<p>
+- Fix inline_set_returning_function() to preserve the invalItems list
+  properly.  This avoids a possible crash when inlining a SRF whose
+  argument list contains a reference to an inline-able user function.
+  The crash is quite reproducible with CLOBBER_FREED_MEMORY enabled,
+  but would be less certain in a production build.  Problem introduced
+  in 9.0 by the named-arguments patch, which requires invoking
+  eval_const_expressions() before we can try to inline a SRF.  Per
+  report from Brendan Jurd.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=ef55e294e66725c412d55b9689328235141d816d">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=ef55e294e66725c412d55b9689328235141d816d</a>
+</p>
+
+<p>
+- Fix overly-enthusiastic Assert in printing of Param reference
+  expressions.  A NestLoopParam's value can only be a Var or Aggref,
+  but this isn't the case in general for SubPlan parameters, so
+  print_parameter_expr had better be prepared to cope.  Brain fade in
+  my recent patch to print the referenced expression instead of just
+  printing $N for PARAM_EXEC Params.  Per report from Pavel Stehule.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=c6873eac4c33720140240cdbd1a663fecc922c57">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=c6873eac4c33720140240cdbd1a663fecc922c57</a>
+</p>
+
+<p>
+- Fix up some oversights in psql's Unicode-escape support.  Original
+  patch failed to include new exclusive states in a switch that needed
+  to include them; and also was guilty of very fuzzy thinking about
+  how to handle error cases.  Per bug #5729 from Alan Choi.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=35d89401525677441824c6f2116b9f7d0cc3caac">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=35d89401525677441824c6f2116b9f7d0cc3caac</a>
+</p>
+
+<p>
+- Previous patch had no detectable virtue other than being a
+  one-liner.  Try to make the code look self-consistent again, so it
+  doesn't confuse future developers.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e6721c6e1617a0fc8b4bce8eacba8b5a381f1f21">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e6721c6e1617a0fc8b4bce8eacba8b5a381f1f21</a>
+</p>
+
+<p>
+- Fix plpgsql's handling of "simple" expression evaluation.  In
+  general, expression execution state trees aren't re-entrantly
+  usable, since functions can store private state information in them.
+  For efficiency reasons, plpgsql tries to cache and reuse state trees
+  for "simple" expressions.  It can get away with that most of the
+  time, but it can fail if the state tree is dirty from a previous
+  failed execution (as in an example from Alvaro) or is being used
+  recursively (as noted by me).  Fix by tracking whether a state tree
+  is in use, and falling back to the "non-simple" code path if so.
+  This results in a pretty considerable speed hit when the non-simple
+  path is taken, but the available alternatives seem even more
+  unpleasant because they add overhead in the simple path.  Per idea
+  from Heikki Linnakangas.  Back-patch to all supported branches.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8ce22dd4c51b6e8155889653c0116cad13877512">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8ce22dd4c51b6e8155889653c0116cad13877512</a>
+</p>
+
+<p>
+- Save a few cycles in plpgsql simple-expression initialization.
+  Instead of using ExecPrepareExpr, call ExecInitExpr.  The net change
+  here is that we don't apply expression_planner() to the expression
+  tree.  There is no need to do so, because that tree is extracted
+  from a fully planned plancache entry, so all the needed work is
+  already done.  This reduces the setup costs by about a factor of 2
+  according to some simple tests.  Oversight noted while fooling
+  around with the simple-expression code for previous fix.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=37e0a016547abb3526b685d7aacbd0a4d57f6937">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=37e0a016547abb3526b685d7aacbd0a4d57f6937</a>
+</p>
+
+<p>
+- In psql, make \? output of \dg and \du the same.  The previous
+  wording might have suggested that \du only showed login roles and
+  \dg only group roles, but that is no longer the case.  Proposed by
+  Josh Kupershmidt.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=299591d1a293e737d72d57aa8545c6c00d19db1d">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=299591d1a293e737d72d57aa8545c6c00d19db1d</a>
+</p>
+
+<p>
+- In psql, add tab completion for psql \dg and \z.  Josh Kupershmidt.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a3d40e9fb51f8aab9cde5d5018be5e46332275fd">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a3d40e9fb51f8aab9cde5d5018be5e46332275fd</a>
+</p>
+
+<p>
+- Avoid creation of useless EquivalenceClasses during planning.
+  Zoltan Boszormenyi exhibited a test case in which planning time was
+  dominated by construction of EquivalenceClasses and PathKeys that
+  had no actual relevance to the query (and in fact got discarded
+  immediately).  This happened because we generated PathKeys
+  describing the sort ordering of every index on every table in the
+  query, and only after that checked to see if the sort ordering was
+  relevant.  The Emmanuel Cecchet/PK construction code is O(N^2) in
+  the number of ECs, which is all right for the intended number of
+  such objects, but it gets out of hand if there are ECs for lots of
+  irrelevant indexes.  To fix, twiddle the handling of mergeclauses a
+  little bit to ensure that every interesting Emmanuel Cecchet is
+  created before we begin path generation.  (This doesn't cost
+  anything --- in fact I think it's a bit cheaper than before ---
+  since we always eventually created those ECs anyway.)  Then, if an
+  index column can't be found in any pre-existing Emmanuel Cecchet, we
+  know that that sort ordering is irrelevant for the query.  Instead
+  of creating a useless Emmanuel Cecchet, we can just not build a
+  pathkey for the index column in the first place.  The index will
+  still be considered if it's useful for non-order-related reasons,
+  but we will think of its output as unsorted.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=14231a41a94b2345cc679ff67dbee1bf7dac7029">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=14231a41a94b2345cc679ff67dbee1bf7dac7029</a>
+</p>
+
+<p>
+- Oops, missed one fix for EquivalenceClass rearrangement.  Now that
+  we're expecting a mergeclause's left_ec/right_ec to persist from the
+  initial assignments, we can't just blithely zero these out when
+  transforming such a clause in adjust_appendrel_attrs.  But really it
+  should be okay to keep the parent's values, since a child table's
+  derived Var ought to be equivalent to the parent Var for all
+  EquivalenceClass purposes.  (Indeed, I'm wondering whether we
+  couldn't find a way to dispense with add_child_rel_equivalences
+  altogether.  But this is wrong in any case.)
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=48a1fb23900d73e7d9cb2dc0408c745cd03597a7">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=48a1fb23900d73e7d9cb2dc0408c745cd03597a7</a>
+</p>
+
+<p>
+- Fix comparisons of pointers with zero to compare with NULL instead.
+  Per C standard, these are semantically the same thing; but saying
+  NULL when you mean NULL is good for readability.  Marti Raudsepp,
+  per results of INRIA's Coccinelle.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bfd3f37be309c3647844aed937e6a66aad5fd3cb">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bfd3f37be309c3647844aed937e6a66aad5fd3cb</a>
+</p>
+
+<p>
+- Provide hashing support for arrays.  The core of this patch is
+  hash_array() and associated typcache infrastructure, which works
+  just about exactly like the existing support for array comparison.
+  In addition I did some work to ensure that the planner won't think
+  that an array type is hashable unless its element type is hashable,
+  and similarly for sorting.  This includes adding a datatype
+  parameter to op_hashjoinable and op_mergejoinable, and adding an
+  explicit "hashable" flag to SortGroupClause.  The lack of a
+  cross-check on the element type was a pre-existing bug in mergejoin
+  support --- but it didn't matter so much before, because if you
+  couldn't sort the element type there wasn't any good alternative to
+  failing anyhow.  Now that we have the alternative of hashing the
+  array type, there are cases where we can avoid a failure by being
+  picky at the planner stage, so it's time to be picky.  The issue of
+  exactly how to combine the per-element hash values to produce an
+  array hash is still open for discussion, but the rest of this is
+  pretty solid, so I'll commit it as-is.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=186cbbda8f8dc5e42f68fc7892f206a76d56a20f">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=186cbbda8f8dc5e42f68fc7892f206a76d56a20f</a>
+</p>
+
+<p>
+- Revert removal of trigger flag from plperl function hash key.  As
+  noted by Jan Urbanski, this flag is in fact needed to ensure that
+  the function's input/result conversion functions are set up as
+  expected.  Add a regression test to discourage anyone from making
+  same mistake in future.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=76b12e0af765b2ca2eeddcabdd5e7c22eda164da">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=76b12e0af765b2ca2eeddcabdd5e7c22eda164da</a>
+</p>
+
+<p>
+Alvaro Herrera pushed:
+</p>
+
+<p>
+- find -path is not portable, so use grep -v instead.  Per previous
+  failure of buildfarm member koi (which is no longer failing, alas).
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9350824e708678f6af9657979ba656cf1951b408">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9350824e708678f6af9657979ba656cf1951b408</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Refactor typenameTypeId() Split the old typenameTypeId() into two
+  functions: A new typenameTypeId() that returns only a type OID, and
+  typenameTypeIdAndMod() that returns type OID and typmod.  This
+  isolates call sites better that actually care about the typmod.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=35670340f57d78d6ab023b1fb42fd81339f85d4c">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=35670340f57d78d6ab023b1fb42fd81339f85d4c</a>
+</p>
+
+<p>
+- Add missing newlines at end of files.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a87d21263600a978ff85142c53375ab25eb30bce">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a87d21263600a978ff85142c53375ab25eb30bce</a>
+</p>
+
+<p>
+- Remove obsolete release-alpha.sgml.  This was only used while the
+  final release notes for 9.0 were being prepared.  The alpha release
+  notes are now in release-9.1.sgml.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=18d6437885d2cf50bb16b09676ff054054591290">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=18d6437885d2cf50bb16b09676ff054054591290</a>
+</p>
+
+<p>
+- Release notes for 9.1alpha2.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e9eb4f401333209139af1acee2cd4251b05e0397">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e9eb4f401333209139af1acee2cd4251b05e0397</a>
+</p>
+
+<p>
+- Remove tabs from SGML.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2999f4ef354a72f00ab0033ed9c0463d89212b99">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2999f4ef354a72f00ab0033ed9c0463d89212b99</a>
+</p>
+
+<p>
+- Last-minute updates to 9.1alpha2 release notes.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=71165685b265a8e5fdd615485917affdb0e8fa32">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=71165685b265a8e5fdd615485917affdb0e8fa32</a>
+</p>
+
+<p>
+- Change version number in release notes to 9.1alpha2
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bd1ff9713369c2f54391112b92e0c22ab5c99180">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bd1ff9713369c2f54391112b92e0c22ab5c99180</a>
+</p>
+
+<p>
+ITAGAKI Takahiro pushed:
+</p>
+
+<p>
+- Add .gitignore for contrib/uuid-ossp.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=07ca728f699694781ce62eae9e2fa61cd4ffa542">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=07ca728f699694781ce62eae9e2fa61cd4ffa542</a>
+</p>
+
+<p>
+- Fix typos "are are".
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bf76ad07fe59affc64f1554d4ff20ddf4d5e8e59">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bf76ad07fe59affc64f1554d4ff20ddf4d5e8e59</a>
+</p>
+
+<p>
+Heikki Linnakangas pushed:
+</p>
+
+<p>
+- Before removing backup_label and irrevocably changing pg_control
+  file, check that WAL file containing the checkpoint redo-location
+  can be found.  This avoids making the cluster irrecoverable if the
+  redo location is in an earlie WAL file than the checkpoint record.
+  Report, analysis and patch by Jeff Davis, with small changes by me.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=0c6293dd0361a0d3c72c94ced389c509019713a7">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=0c6293dd0361a0d3c72c94ced389c509019713a7</a>
+</p>
+
+<p>
+- Note explicitly that hash indexes are also not replicated because
+  they're not WAL-logged.  Make the notice about the lack of
+  WAL-logging more visible by making it a <caution>.  Also remove the
+  false statement from hot standby caveats section that hash indexes
+  are not used during hot standby.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5c38782cc8b3219d43ac2ccaf4254fd590bde758">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5c38782cc8b3219d43ac2ccaf4254fd590bde758</a>
+</p>
+
+<p>
+- Fix long-standing segfault when accept() or one of the calls made
+  right after accepting a connection fails, and the server is compiled
+  with GSSAPI support. Report and patch by Alexander V. Chernikov, bug
+  #5731.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=869af50fcfdd4448b2dc637d905f1afda689741d">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=869af50fcfdd4448b2dc637d905f1afda689741d</a>
+</p>
+
+<p>
+- Give a more specific error message if you try to COMMIT, ROLLBACK or
+  COPY FROM STDIN in PL/pgSQL. We alread did this for dynamic EXECUTE
+  statements, ie. "EXECUTE 'COMMIT'", but not otherwise.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f184de351d6a35355aa8f1c1b655c3f6a5087205">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f184de351d6a35355aa8f1c1b655c3f6a5087205</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Fix dumb typo in SECURITY LABEL error message.  Report by Peter
+  Eisentraut.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3579a94d6acd9374fbc3b45d0be593331ffd414d">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3579a94d6acd9374fbc3b45d0be593331ffd414d</a>
+</p>
+
+<p>
+- Minor fixups for psql's process_file() function.  Avoid closing
+  stdin, since we didn't open it.  Previously multiple inclusions of
+  stdin would be terminated with a single quit, now a separate quit is
+  needed for each invocation. Previous behavior also accessed stdin
+  after it was fclose()d, which is undefined behavior per ANSI C.
+  Properly restore pset.inputfile, since the caller expects to be able
+  to free that memory.  Marti Raudsepp.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1fea0c05eb4ac4a21d79471b9a7fe96163306b88">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1fea0c05eb4ac4a21d79471b9a7fe96163306b88</a>
+</p>
+
+<p>
+- Add a client authentication hook.  KaiGai Kohei, with minor cleanup
+  of the comments by me.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=20709f813601976076a346c0b0f8e92006e3b3fa">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=20709f813601976076a346c0b0f8e92006e3b3fa</a>
+</p>
+
+<p>
+- Note that effective_io_concurrency only affects bitmap heap scans.
+  Josh Kupershmidt.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5a12c808cf223c7a5498217142cc9cb45efe033a">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5a12c808cf223c7a5498217142cc9cb45efe033a</a>
+</p>
+
+<p>
+- Reorganize OS-specific details about write caching into a list.
+  Along the way, clarify that sdparm can be used on Linux as well as
+  FreeBSD.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=0d5deebe11818a54f79ca66e1a1d41dae0e0b52b">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=0d5deebe11818a54f79ca66e1a1d41dae0e0b52b</a>
+</p>
+
+<p>
+- Revert "Correct WAL space calculation formula in docs." This reverts
+  commit 915116bc62db2aaec7001bde6610128f4cbd29f9.  Per discussion,
+  the previous formula was in fact correct.
+  <a href="http://archives.postgresql.org/pgsql-docs/2010-10/msg00038.php">http://archives.postgresql.org/pgsql-docs/2010-10/msg00038.php</a>
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2cae0aeb9c61aef48b6de3fb5c4f7785a06bca0b">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2cae0aeb9c61aef48b6de3fb5c4f7785a06bca0b</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Allow generic record arguments to plperl functions.
+  <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6c3c7b533e4b73bef99996f92da26c7c4124edd3">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6c3c7b533e4b73bef99996f92da26c7c4124edd3</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Shigeru HANADA sent in another revision of the patch to add SQL/MED
+with simple wrappers.
+</p>
+
+<p>
+ITAGAKI Takahiro sent in two revisions of a patch to add executor
+nodes, which will help with, among other things, SQL/MED.
+</p>
+
+<p>
+Alvaro Herrera sent in a patch atop the patch to add EXTENSIONs.
+</p>
+
+<p>
+David Fetter sent in two revisions of a patch to add tab completion in
+psql for views made writeable by triggers.
+</p>
+
+<p>
+Dimitri Fontaine sent in another patch for EXTENSIONs.
+</p>
+
+<p>
+Zoltan Boszormenyi, Heikki Linnakangas and Tom Lane traded patches to
+speed up planning times for queries on tables with large numbers of
+partitions.
+</p>
+
+<p>
+Alvaro Herrera sent in a patch to add "ALTER TYPE...ADD ELEMENT" to
+enums.
+</p>
+
+<p>
+Steve Singer sent in a patch to modify TRUNCATE ... RESTART IDENTITY
+so that when the transaction rolls back, the restart of the sequence
+also rolls back.
+</p>
+
+<p>
+Robert Haas sent in a patch to help explain about sdparm's effects on
+WAL durability.
+</p>
+
+<p>
+Alvaro Herrera sent in a patch to change ALTER TYPE...ENUM... to
+include ADD LABEL [BEFORE|AFTER].  The LABEL is new.
+</p>
+
+<p>
+Zoltan Boszormenyi sent in a patch for ECPG to get WHERE CURRENT OF to
+accept dynamic cursor names.
+</p>
+
+<p>
+Heikki Linnakangas sent in a patch to allow tracking the latest
+timeline in standby mode.
+</p>
+
+<p>
+Marti Raudsepp sent in a patch to change places where pointers were
+compared to 0 to compare them to NULL.
+</p>
+
+<p>
+Alexander Korotkov sent in a patch to fix the GiST picksplit method
+implementation in contrib/cube.
+</p>
+
+<p>
+Andres Freund sent in another revision of the patch to cancel IIT
+backends.
+</p>
+
+<p>
+Marti Raudsepp sent in some more fixes based on Coccinelli runs.
+</p>
+
+<p>
+Dimitri Fontaine sent in a patch to add ALTER...SET SCHEMA... to those
+object types that don't already have it.
+</p>
+
+<p>
+Peter Eisentraut sent in a patch to avoid passing around type OID +
+typmod (+ collation) separately all over the place.  Instead, there is
+a new struct TypeInfo that contains these fields, and only a pointer
+is passed around.
+</p>
+
+<p>
+Alex Hunsaker sent in a patch to fix another issue with PL/Perl
+trigger functions.
+</p>
+
+<p>
+Andres Freund sent in a patch to improve the performance of int32- and
+int64-to-text conversions by creating a custom converter rather than
+using the standard itoa functions.
+
+</p>
+