--- /dev/null
+<!-- BEGIN page_title_block -->
+Weekly News - December 12 2010
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - December 12 2010</h1>
+
+<p>
+The Call for Papers is still open for the PostgreSQL room at FOSDEM,
+which will be held in Brussels, Belgium, on February 5-6, 2011. Send
+your proposals to fosdem AT postgresql DOT eu.
+</p>
+
+<p>
+Devrim GUNDUZ sent in a fix for the RHEL6 RPMs. See below for
+details.
+<a href="http://people.planetpostgresql.org/devrim/index.php?/archives/54-Attention-9.0.1-OR-RHEL-6-RPM-users.html">http://people.planetpostgresql.org/devrim/index.php?/archives/54-Attention-9.0.1-OR-RHEL-6-RPM-users.html</a>
+</p>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+PostgreSQL Maestro 10.12, a GUI admin tool for PostgreSQL, released.
+<a href="http://www.sqlmaestro.com/products/postgresql/maestro/">http://www.sqlmaestro.com/products/postgresql/maestro/</a>
+</p>
+
+<p>
+psycopg2 2.3.1, a Python connector for PostgreSQL, released.
+<a href="http://initd.org/psycopg/articles/2010/12/04/psycopg-231-released/">http://initd.org/psycopg/articles/2010/12/04/psycopg-231-released/</a>
+</p>
+
+<p>
+Slony-I, a master-to-multiple-cascading-replica system for PostgreSQL,
+released updated revisions 1.2.22 and 2.0.6.
+<a href="http://www.slony.info/">http://www.slony.info/</a>
+</p>
+
+<h2>PostgreSQL Jobs for December</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2010-12/threads.php">http://archives.postgresql.org/pgsql-jobs/2010-12/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+The PostgreSQLFr Call for Projects has begun. Projects must target
+PostgreSQL and the French-speaking community. Mail appel-projets-2010
+AT postgresql DOT fr.
+<a href="http://www.postgresql.fr/appel_a_projets_2010:call_for_projects">http://www.postgresql.fr/appel_a_projets_2010:call_for_projects</a>
+</p>
+
+<p>
+FOSDEM is one of the biggest Free and Open Source event held annually
+in Brussels, Belgium, on February 5-6, 2011, and attended by around
+4000 people. Send in your proposal to fosdem AT postgresql DOT eu.
+<a href="http://andreas.scherbaum.la/blog/archives/749-PostgreSQLFOSDEM-2011-Call-for-talks.html">http://andreas.scherbaum.la/blog/archives/749-PostgreSQLFOSDEM-2011-Call-for-talks.html</a>
+</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, 2011. Post your talk submission
+to pgday-submissions AT googlegroups DOT com.
+</p>
+
+<p>
+PGCon will be May 19-20, 2011 at the University of Ottawa, preceded by
+two days of tutorials on May 17-18.
+<a href="http://www.pgcon.org/2011/">http://www.pgcon.org/2011/</a>
+</p>
+
+<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>
+<p>
+ITAGAKI Takahiro reviewed the per-column collation patch, bringing up
+issues with pg_dump, along with a couple of naming issues in the
+source code and a request for clearer global state.
+== Applied Patches ==
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Put only single space after "Sort Method:", for consistency.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=951d7861212120571a601d946194892db6f2bde1">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=951d7861212120571a601d946194892db6f2bde1</a>
+</p>
+
+<p>
+Heikki Linnakangas pushed:
+</p>
+
+<p>
+- Fix two typos, by Fujii Masao.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=95e42a2c2980003880dee622fc3bed0b03322542">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=95e42a2c2980003880dee622fc3bed0b03322542</a>
+</p>
+
+<p>
+- Fix bugs in the hot standby known-assigned-xids tracking logic. If
+ there's an old transaction running in the master, and a lot of
+ transactions have started and finished since, and a WAL-record is
+ written in the gap between the creating the running-xacts snapshot
+ and WAL-logging it, recovery will fail with "too many
+ KnownAssignedXids" error. This bug was reported by Joachim Wieland
+ on Nov 19th. In the same scenario, when fewer transactions have
+ started so that all the xids fit in KnownAssignedXids despite the
+ first bug, a more serious bug arises. We incorrectly initialize the
+ clog code with the oldest still running transaction, and when we see
+ the WAL record belonging to a transaction with an XID larger than
+ one that committed already before the checkpoint we're recovering
+ from, we zero the clog page containing the already committed
+ transaction, leading to data loss. In hindsight, trying to track
+ xids in the known-assigned-xids array before seeing the
+ running-xacts record was too complicated. To fix that, hold
+ XidGenLock while the running-xacts snapshot is taken and WAL-logged.
+ That ensures that no transaction can begin or end in that gap, so
+ that in recvoery we know that the snapshot contains all transactions
+ running at that point in WAL.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5a031a5556ff83b8a9646892715d7fef415b83c3">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5a031a5556ff83b8a9646892715d7fef415b83c3</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Allow the low level COPY routines to read arbitrary numbers of
+ fields. This doesn't involve any user-visible change in behavior,
+ but will be useful when the COPY routines are exposed to allow their
+ use by Foreign Data Wrapper routines, which will be able to use
+ these routines to read irregular CSV files, for example.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=af1a614ec6d074fdea46de2e1c462f23fc7ddc6f">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=af1a614ec6d074fdea46de2e1c462f23fc7ddc6f</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Add a stack overflow check to copyObject(). There are some code
+ paths, such as SPI_execute(), where we invoke copyObject() on raw
+ parse trees before doing parse analysis on them. Since the bison
+ grammar is capable of building heavily nested parsetrees while
+ itself using only minimal stack depth, this means that copyObject()
+ can be the front-line function that hits stack overflow before
+ anything else does. Accordingly, it had better have a
+ check_stack_depth() call. I did a bit of performance testing and
+ found that this slows down copyObject() by only a few percent, so
+ the hit ought to be negligible in the context of complete processing
+ of a query. Per off-list report from Toshihide Katayama.
+ Back-patch to all supported branches.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8b5692809707c0e15d04c530a3fed9347350ea01">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8b5692809707c0e15d04c530a3fed9347350ea01</a>
+</p>
+
+<p>
+- Force default wal_sync_method to be fdatasync on Linux. Recent
+ versions of the Linux system header files cause xlogdefs.h to
+ believe that open_datasync should be the default sync method,
+ whereas formerly fdatasync was the default on Linux. open_datasync
+ is a bad choice, first because it doesn't actually outperform
+ fdatasync (in fact the reverse), and second because we try to use
+ O_DIRECT with it, causing failures on certain filesystems (e.g.,
+ ext4 with data=journal option). This part of the patch is largely
+ per a proposal from Marti Raudsepp. More extensive changes are
+ likely to follow in HEAD, but this is as much change as we want to
+ back-patch. Also clean up confusing code and incorrect
+ documentation surrounding the fsync_writethrough option. Those
+ changes shouldn't result in any actual behavioral change, but I
+ chose to back-patch them anyway to keep the branches looking similar
+ in this area. In 9.0 and HEAD, also do some copy-editing on the WAL
+ Reliability documentation section. Back-patch to all supported
+ branches, since any of them might get used on modern Linux versions.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=576477e73c4a9cb32c7471c1cec354fd5328140e">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=576477e73c4a9cb32c7471c1cec354fd5328140e</a>
+</p>
+
+<p>
+- Clean up some copied-and-pasted code in pg_upgrade. 1. Don't
+ reimplement S_ISDIR() and S_ISREG() badly. 2. Don't reimplement
+ access() badly. This code appears to have been copied from ancient
+ versions of the corresponding backend routines, and not patched to
+ incorporate subsequent fixes (see my commits of 2008-03-31 and
+ 2010-01-14 respectively). It might be a good idea to change it to
+ just *call* those routines, but for now I'll just transpose these
+ fixes over.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=663fc32e26e8df41434d751e2203c1aa410d1916">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=663fc32e26e8df41434d751e2203c1aa410d1916</a>
+</p>
+
+<p>
+- Make S_IRGRP etc available in mingw builds as well as MSVC. (Hm, I
+ wonder whether BCC defines them either...) Also label dangling
+ endifs a bit better in this area.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5132ad8bdf8e85ea0054217ef7ee38c51ace4824">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5132ad8bdf8e85ea0054217ef7ee38c51ace4824</a>
+</p>
+
+<p>
+- Reset all database-level stats in pgstat_recv_resetcounter(). We
+ were failing to zero out some pg_stat_database counters that have
+ been added since the initial pgstats coding. This is a bug, but not
+ back-patching the fix since changing this behavior in a minor
+ release seems a cure worse than the disease. Report and patch by
+ Tomas Vondra.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=0c90442355fbbe785740669f63141f24674c8958">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=0c90442355fbbe785740669f63141f24674c8958</a>
+</p>
+
+<p>
+Simon Riggs pushed:
+</p>
+
+<p>
+- Optimize commit_siblings in two ways to improve group commit.
+ First, avoid scanning the whole ProcArray once we know there are at
+ least commit_siblings active; second, skip the check altogether if
+ commit_siblings = 0. Greg Smith.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e620ee35b249b0af255ef788003d1c9edb815a35">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e620ee35b249b0af255ef788003d1c9edb815a35</a>
+</p>
+
+<p>
+- Reduce spurious Hot Standby conflicts from never-visible records.
+ Hot Standby conflicts only with tuples that were visible at some
+ point. So ignore tuples from aborted transactions or for tuples
+ updated/deleted during the inserting transaction when generating the
+ conflict transaction ids. Following detailed analysis and test case
+ by Noah Misch. Original report covered btree delete records,
+ correctly observed by Heikki Linnakangas that this applies to other
+ cases also. Fix covers all sources of cleanup records via common
+ code.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b9075a6d2f9b07a00262a670dd60272904c79dce">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b9075a6d2f9b07a00262a670dd60272904c79dce</a>
+</p>
+
+<p>
+- Self review of previous patch. Fix assumption that xmax >= xmin.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9975c683b102d06ed5d5ab799eaba0d00a9ff38c">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9975c683b102d06ed5d5ab799eaba0d00a9ff38c</a>
+</p>
+
+<p>
+- Reduce spurious Hot Standby conflicts from never-visible records.
+ Hot Standby conflicts only with tuples that were visible at some
+ point. So ignore tuples from aborted transactions or for tuples
+ updated/deleted during the inserting transaction when generating the
+ conflict transaction ids. Following detailed analysis and test case
+ by Noah Misch. Original report covered btree delete records,
+ correctly observed by Heikki Linnakangas that this applies to other
+ cases also. Fix covers all sources of cleanup records via common
+ code. Includes additional fix compared to commit on HEAD
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a804a23e7af0e075b88e7b03bfd9b0f22d2657b2">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a804a23e7af0e075b88e7b03bfd9b0f22d2657b2</a>
+</p>
+
+<p>
+Robert Haas pushed:
+</p>
+
+<p>
+- Minor documentation cleanup. Fujii Masao
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1490946c57f44d3bf8601e9a404aaa80b58a715a">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1490946c57f44d3bf8601e9a404aaa80b58a715a</a>
+</p>
+
+<p>
+- Allow bidirectional copy messages in streaming replication mode.
+ Fujii Masao. Review by Alvaro Herrera, Tom Lane, and myself.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d3d414696f39e2b57072fab3dd4fa11e465be4ed">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d3d414696f39e2b57072fab3dd4fa11e465be4ed</a>
+</p>
+
+<p>
+Magnus Hagander pushed:
+</p>
+
+<p>
+- Add required new port files to MSVC builds.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=20f396429186a35a81fc7ef3ad34c3134ead2992">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=20f396429186a35a81fc7ef3ad34c3134ead2992</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Joachim Wieland sent in another revision of the patch to clone
+snapshots and make them available.
+</p>
+
+<p>
+Craig Ringer sent in a patch to add a crash dump, similar to a core
+dump, only for Windows.
+</p>
+
+<p>
+Josh Berkus sent in two revisions of a patch to make wal_sync_method
+default to fdatasync on Linux kernels 2.6.33 and higher.
+</p>
+
+<p>
+Fujii Masao sent in another revision of the patch to change libpq to
+help with synchronous replication.
+</p>
+
+<p>
+Fujii Masao sent in a patch to set a replication timeout. This, too,
+is intended to help with synchronous replication.
+</p>
+
+<p>
+Peter Eisentraut sent in a patch to add a pg_sequence_parameters()
+function.
+</p>
+
+<p>
+KaiGai Kohei sent in another revision of the access control label
+switcher function.
+</p>
+
+<p>
+Joachim Wieland sent in another revision of the patch to add a
+directory-based format for pg_dump/pg_restore.
+</p>
+
+<p>
+Fujii Masao sent in a patch to remove wal_sender_delay.
+</p>
+
+<p>
+Tim Bunce sent in a patch to optimize argument-passing in PL/Perl[U].
+</p>
+
+<p>
+Kevin Grittner sent in four revisions of a patch to add a optimize and
+correct SERIALIZABLE so that it doesn't switch from READ ONLY
+DEFERRABLE mode to READ WRITE.
+</p>
+
+<p>
+Tom Lane sent in a patch to fix some infelicities in the speed of
+calculating percent_rank() vs. rank().
+</p>
+
+<p>
+Fujii Masao sent in a patch to fix the way ps(1) displays standby
+queries.
+</p>
+
+<p>
+Dimitri Fontaine sent in two more revisions to add extensions.
+</p>
+
+<p>
+Robert Haas sent in another revision of the patch to add unlogged
+tables.
+</p>
+
+<p>
+Thomas (tv AT fuzzy DOT cz) sent in two revisions of a patch to keep a
+timestamp of the most recent stats reset per-database, per-table, and
+per-function.
+</p>
+
+<p>
+Dimitri Fontaine sent in another revision of the patch to add a
+pg_execute_from_file() function. This is part of the EXTENSIONS work.
+</p>
+
+<p>
+Alexander Korotkov sent in a patch to add wildcard support for
+pg_trgm.
+</p>
+
+<p>
+Simon Riggs sent in a patch to add a NOT ENFORCED clause to foreign
+key constraints.
+</p>
+
+<p>
+Peter Eisentraut sent in another revision of the per-column collation
+patch.
+</p>
+
+<p>
+ITAGAKI Takahiro sent in another revision of the patch to add
+file_fdw(), part of the SQL/MED standard dealing with reading and
+writing external files.
+
+</p>
+
--- /dev/null
+<!-- BEGIN page_title_block -->
+Weekly News - December 19 2010
+<!-- END page_title_block -->
+
+<h1>PostgreSQL Weekly News - December 19 2010</h1>
+
+<p>
+PostgreSQL 9.0.2, 8.4.6, 8.3.13, 8.2.19, 8.1.23 updates released. If
+you are using Hot or Warm Standby, or PITR, you should upgrade as soon
+as possible. The 8.1 series is now end-of-life, and users are
+encouraged to upgrade to a newer major version as soon as possible.
+<a href="http://www.postgresql.org/docs/9.0/static/release.html">http://www.postgresql.org/docs/9.0/static/release.html</a>
+</p>
+
+<p>
+Submit a proposal for PGCon 2011.
+<a href="http://lists.pgcon.org/pipermail/pgcon-announce/2010-December/000065.html">http://lists.pgcon.org/pipermail/pgcon-announce/2010-December/000065.html</a>
+</p>
+
+<p>
+The Call for Papers for the fourth annual Prague PostgreSQL
+Developers' Day is open. It will be held February 10, 2011 at Charles
+University in Prague.
+<a href="http://archives.postgresql.org/pgsql-announce/2010-12/msg00009.php">http://archives.postgresql.org/pgsql-announce/2010-12/msg00009.php</a>
+</p>
+
+<p>
+PostgreSQL Conference East 2011: NYC March 22nd - 25th
+<a href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a>
+</p>
+
+<h2>PostgreSQL Product News</h2>
+<p>
+DBD::Pg 2.17.2, a Perl driver for PostgreSQL, released.
+<a href="http://search.cpan.org/dist/DBD-Pg/">http://search.cpan.org/dist/DBD-Pg/</a>
+</p>
+
+<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>
+MicroOLAP has release PaGoDump and PaGoRestore with PostgreSQL 9.0
+support.
+<a href="http://microolap.com/products/database/pagodump/download/">http://microolap.com/products/database/pagodump/download/</a>
+</p>
+
+<p>
+PGSI 1.5.0, a tool which reports overall impact of PostgreSQL queries
+on a server, released:
+<a href="http://bucardo.org/wiki/Pgsi">http://bucardo.org/wiki/Pgsi</a>
+</p>
+
+<p>
+phpPgAdmin 5.0.1, a web-based administrative tool for PostgreSQL, released.
+<a href="http://phppgadmin.sourceforge.net/">http://phppgadmin.sourceforge.net/</a>
+</p>
+
+<p>
+Printed versions of the PostgreSQL 9.0.1 manual are available.
+<a href="http://www.network-theory.co.uk/postgresql9/">http://www.network-theory.co.uk/postgresql9/</a>
+</p>
+
+<p>
+Data Visualization 0.9.2, which supports PostgreSQL, released.
+<a href="http://sites.google.com/site/datavisualizationapplication/">http://sites.google.com/site/datavisualizationapplication/</a>
+</p>
+
+<h2>PostgreSQL Jobs for December</h2>
+<p>
+<a href="http://archives.postgresql.org/pgsql-jobs/2010-12/threads.php">http://archives.postgresql.org/pgsql-jobs/2010-12/threads.php</a>
+</p>
+
+<h2>PostgreSQL Local</h2>
+<p>
+The PostgreSQLFr Call for Projects has begun. Projects must target
+PostgreSQL and the French-speaking community. Mail appel-projets-2010
+AT postgresql DOT fr.
+<a href="http://www.postgresql.fr/appel_a_projets_2010:call_for_projects">http://www.postgresql.fr/appel_a_projets_2010:call_for_projects</a>
+</p>
+
+<p>
+FOSDEM is one of the biggest Free and Open Source event held annually
+in Brussels, Belgium, on February 5-6, 2011, and attended by around
+4000 people. Send in your proposal to fosdem AT postgresql DOT eu.
+<a href="http://andreas.scherbaum.la/blog/archives/749-PostgreSQLFOSDEM-2011-Call-for-talks.html">http://andreas.scherbaum.la/blog/archives/749-PostgreSQLFOSDEM-2011-Call-for-talks.html</a>
+</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, 2011. Post your talk submission
+to pgday-submissions AT googlegroups DOT com.
+</p>
+
+<p>
+PGCon will be May 19-20, 2011 at the University of Ottawa, preceded by
+two days of tutorials on May 17-18. The Call for Papers is open!
+<a href="http://www.pgcon.org/2011/">http://www.pgcon.org/2011/</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>
+Robert Haas pushed:
+</p>
+
+<p>
+- Generalize concept of temporary relations to "relation persistence".
+ This commit replaces pg_class.relistemp with
+ pg_class.relpersistence; and also modifies the RangeVar node type to
+ carry relpersistence rather than istemp. It also removes removes
+ rd_istemp from RelationData and instead performs the correct
+ computation based on relpersistence. For clarity, we add three new
+ macros: RelationNeedsWAL(), RelationUsesLocalBuffers(), and
+ RelationUsesTempNamespace(), so that we can clarify the purpose of
+ each check that previous depended on rd_istemp. This is intended as
+ infrastructure for the upcoming unlogged tables patch, as well as
+ for future possible work on global temporary tables.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5f7b58fad8f45c69bb67944779dce67e2f481995">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5f7b58fad8f45c69bb67944779dce67e2f481995</a>
+</p>
+
+<p>
+- Document replacement of pg_class.relistemp with relpersistence.
+ Noted by Tom Lane.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d26849ee26e46a689fb7c228f98e10fb46c1b2a8">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d26849ee26e46a689fb7c228f98e10fb46c1b2a8</a>
+</p>
+
+<p>
+- Allow plugins to suppress inlining and hook function
+ entry/exit/abort. This is intended as infrastructure to allow an
+ eventual SE-Linux plugin to support trusted procedures. KaiGai
+ Kohei.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d368e1a2a7afad5a0fc711a2ab70a83c36fa57af">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d368e1a2a7afad5a0fc711a2ab70a83c36fa57af</a>
+</p>
+
+<p>
+- Improved tab completion for views with triggers. Allow INSERT INTO,
+ UPDATE, and DELETE FROM to be completed with either the name of a
+ table (as before) or the name of a view with an appropriate INSTEAD
+ OF rule. Along the way, allow CREATE TRIGGER to be completed with
+ INSTEAD OF, as well as BEFORE and AFTER. David Fetter, reviewed by
+ Itagaki Takahiro
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9878e295dc937c664367875dc001b7503df057f1">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9878e295dc937c664367875dc001b7503df057f1</a>
+</p>
+
+<p>
+- Instrument checkpoint sync calls. Greg Smith, reviewed by Jeff
+ Janes.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=34c70c7ac4926495b7ab5ebfe748704313a4c822">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=34c70c7ac4926495b7ab5ebfe748704313a4c822</a>
+</p>
+
+<p>
+- Document timestamptz a little better.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=afc8f47b5885716db716a2523c00f7465cb7f415">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=afc8f47b5885716db716a2523c00f7465cb7f415</a>
+</p>
+
+<p>
+- Some copy editing of pg_read_binary_file() patch.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=290f1603b4208ca6a13776f744b586a958e98d74">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=290f1603b4208ca6a13776f744b586a958e98d74</a>
+</p>
+
+<p>
+- Waiting for complete startup is now a well-defined operation. Per
+ report from Fujii Masao, and subsequent discussion.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=df142bf82c84de5d0588ae7d52881501abb039ed">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=df142bf82c84de5d0588ae7d52881501abb039ed</a>
+</p>
+
+<p>
+- Reset 'ps' display just once when resolving VXID conflicts. This
+ prevents the word "waiting" from briefly disappearing from the ps
+ status line when ResolveRecoveryConflictWithVirtualXIDs begins a new
+ iteration of the outer loop. Along the way, remove some useless
+ pgstat_report_waiting() calls; the startup process doesn't appear in
+ pg_stat_activity. Fujii Masao.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=611fed371227f430e71d0ff7fed037f1006b410d">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=611fed371227f430e71d0ff7fed037f1006b410d</a>
+</p>
+
+<p>
+- Try to save a kernel call in ResolveRecoveryConflictWithVirtualXIDs.
+ If there's no work to be done, just exit quickly, before initialization.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8bd4b89e240cc6488f5e1523202cc2d27e9970c0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8bd4b89e240cc6488f5e1523202cc2d27e9970c0</a>
+</p>
+
+<p>
+Tom Lane pushed:
+</p>
+
+<p>
+- Update time zone data files to tzdata release 2010o: DST law changes
+ in Fiji and Samoa. Historical corrections for Hong Kong.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f5e4f743e6a84884156ac86948277df4c672865c">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f5e4f743e6a84884156ac86948277df4c672865c</a>
+</p>
+
+<p>
+- Update release notes for releases 9.0.2, 8.4.6, 8.3.13, 8.2.19, and
+ 8.1.23.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f9224c8ec2f6dcfed6daa3f94597b870ec31c8d8">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f9224c8ec2f6dcfed6daa3f94597b870ec31c8d8</a>
+</p>
+
+<p>
+- Fix contrib/seg's GiST picksplit method. This patch replaces
+ Guttman's generalized split method with a simple
+ sort-by-center-points algorithm. Since the data is only
+ one-dimensional we don't really need the slow and none-too-stable
+ Guttman method. This is in part a bug fix, since seg has the same
+ size_alpha versus size_beta typo that was recently fixed in
+ contrib/cube. It seems prudent to apply this rather aggressive fix
+ only in HEAD, though. Back branches will just get the typo fix.
+ Alexander Korotkov, reviewed by Yeb Havinga.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2a6ebe70fb2f7ec97a08dc07214fe2ca571d2780">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2a6ebe70fb2f7ec97a08dc07214fe2ca571d2780</a>
+</p>
+
+<p>
+- Fix up getopt() reset management so it works on recent mingw. The
+ mingw people don't appear to care about compatibility with non-GNU
+ versions of getopt, so force use of our own copy of getopt on
+ Windows. Also, ensure that we make use of optreset when using our
+ own copy. Per report from Andrew Dunstan. Back-patch to all
+ versions supported on Windows.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5cdd65f3241ce10c66953228daef60df7b3966d1">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5cdd65f3241ce10c66953228daef60df7b3966d1</a>
+</p>
+
+<p>
+- Remove optreset from src/port/ implementations of getopt and
+ getopt_long. We don't actually need optreset, because we can easily
+ fix the code to ensure that it's cleanly restartable after having
+ completed a scan over the argv array; which is the only case we need
+ to restart in. Getting rid of it avoids a class of interactions
+ with the system libraries and allows reversion of my change of
+ yesterday in postmaster.c and postgres.c. Back-patch to 8.4.
+ Before that the getopt code was a bit different anyway.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=61b53695fbbedb7fa9d394e71bf2affdc494e6b0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=61b53695fbbedb7fa9d394e71bf2affdc494e6b0</a>
+</p>
+
+<p>
+- Improve comments around startup_hacks() code. These comments were
+ not updated when we added the EXEC_BACKEND mechanism for Windows,
+ even though it rendered them inaccurate. Also unify two
+ unnecessarily-separate #ifdef __alpha code blocks.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=14ed7735f5bb5275da13891c4bb106c198d00b53">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=14ed7735f5bb5275da13891c4bb106c198d00b53</a>
+</p>
+
+<p>
+- Fix erroneous parsing of tsquery input "... & !(subexpression) |
+ ..." After parsing a parenthesized subexpression, we must pop all
+ pending ANDs and NOTs off the stack, just like the case for a simple
+ operand. Per bug #5793. Also fix clones of this routine in
+ contrib/intarray and contrib/ltree, where input of types query_int
+ and ltxtquery had the same problem. Back-patch to all supported
+ versions.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=abc10262696e53773c9a8c9f279bbd464b464190">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=abc10262696e53773c9a8c9f279bbd464b464190</a>
+</p>
+
+<p>
+- Fix up handling of simple-form CASE with constant test expression.
+ eval_const_expressions() can replace CaseTestExprs with constants
+ when the surrounding CASE's test expression is a constant. This
+ confuses ruleutils.c's heuristic for deparsing simple-form CASEs,
+ leading to Assert failures or "unexpected CASE WHEN clause" errors.
+ I had put in a hack solution for that years ago (see commit
+ 514ce7a331c5bea8e55b106d624e55732a002295 of 2006-10-01), but bug
+ #5794 from Peter Speck shows that that solution failed to cover all
+ cases. Fortunately, there's a much better way, which came to me
+ upon reflecting that Peter's "CASE TRUE WHEN" seemed pretty
+ redundant: we can "simplify" the simple-form CASE to the general
+ form of CASE, by simply omitting the constant test expression from
+ the rebuilt CASE construct. This is intuitively valid because there
+ is no need for the executor to evaluate the test expression at
+ runtime; it will never be referenced, because any CaseTestExprs that
+ would have referenced it are now replaced by constants. This won't
+ save a whole lot of cycles, since evaluating a Const is pretty
+ cheap, but a cycle saved is a cycle earned. In any case it beats
+ kluging ruleutils.c still further. So this patch improves
+ const-simplification and reverts the previous change in ruleutils.c.
+ Back-patch to all supported branches. The bug exists in 8.1 too,
+ but it's out of warranty.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1b19e2c0baedb959650a27f25bd8537bd51d60b0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1b19e2c0baedb959650a27f25bd8537bd51d60b0</a>
+</p>
+
+<p>
+Peter Eisentraut pushed:
+</p>
+
+<p>
+- Translation updates for 9.0.2, 8.4.6, 8.3.13, 8.2.19, 8.1.23.
+</p>
+
+<p>
+- Remove recently reintroduced CVS keyword
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=843a490f0aeccd5b61a30c37d2ffaae26d192329">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=843a490f0aeccd5b61a30c37d2ffaae26d192329</a>
+</p>
+
+<p>
+Marc Fournier pushed:
+</p>
+
+<p>
+- Tag 9.0.2, 8.4.6, 8.3.13, 8.2.19, 8.1.23.
+</p>
+
+<p>
+Bruce Momjian pushed:
+</p>
+
+<p>
+- Use "upgrade" in preference over "migrate" in pg_upgrade messages
+ and documentation. (Many were left over from the old pg_migrator
+ naming.)
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=16b5e08decc8207ae35589add387dce9b62669de">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=16b5e08decc8207ae35589add387dce9b62669de</a>
+</p>
+
+<p>
+- Fix crash caused by NULL lookup when reporting IP address of failed
+ libpq connection, per report from Magnus. This happens only on GIT
+ master and only on Win32 because that is the platform where "" maps
+ to an IP address (localhost).
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=48da2b87e3f292534a26d3bacc2a13f7b62a34c8">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=48da2b87e3f292534a26d3bacc2a13f7b62a34c8</a>
+</p>
+
+<p>
+- Properly print the IP number and "localhost" for failed localhost
+ connections when the server is down, on Win32.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=7e95337d586185c91f8af3fbcb0a6b380b4ba1c7">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=7e95337d586185c91f8af3fbcb0a6b380b4ba1c7</a>
+</p>
+
+<p>
+ITAGAKI Takahiro pushed:
+</p>
+
+<p>
+- Add pg_read_binary_file() and whole-file-at-once versions of
+ pg_read_file(). One of the usages of the binary version is to read
+ files in a different encoding from the server encoding. Dimitri
+ Fontaine and Itagaki Takahiro.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=03db44eae3e065174d5e29888b8d98c39b1f520b">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=03db44eae3e065174d5e29888b8d98c39b1f520b</a>
+</p>
+
+<p>
+Alvaro Herrera pushed:
+</p>
+
+<p>
+- Add some minor missing error checks.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e359b8496d11befb63d4734874d997909c44ad83">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e359b8496d11befb63d4734874d997909c44ad83</a>
+</p>
+
+<p>
+- Simplify SignalSomeChildren(BACKEND_TYPE_ALL) to SignalChildren().
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=16ca75baebc56cebc6590691a0b474ee1922519c">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=16ca75baebc56cebc6590691a0b474ee1922519c</a>
+</p>
+
+<p>
+- Fix inconsequential FILE pointer leakage.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=83c759ea0ea8ffe07c45e6fd2c489cebce2caad6">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=83c759ea0ea8ffe07c45e6fd2c489cebce2caad6</a>
+</p>
+
+<p>
+- Avoid clobbering errno, per comment from Tom Lane.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=cd1fefa973968ff4e3760a9593f70fe2da0def48">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=cd1fefa973968ff4e3760a9593f70fe2da0def48</a>
+</p>
+
+<p>
+- Remove unnecessary definition for autovacuum in SignalSomeChildren.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b68193c0c7a7cfbc4aead3910cd492be63c0cd8b">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b68193c0c7a7cfbc4aead3910cd492be63c0cd8b</a>
+</p>
+
+<p>
+- set_ps_display when calling functions via fastpath. This improves
+ tag output by log_line_prefix.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3026027ec3a795745e8e80fc9f204bebc97be58e">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3026027ec3a795745e8e80fc9f204bebc97be58e</a>
+</p>
+
+<p>
+Andrew Dunstan pushed:
+</p>
+
+<p>
+- Backpatch plperl GNUmakefile fixes to allow building release 8.2 on
+ Mingw with a modern perl.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f2f63551cdafcdec4169557122522229aa2530e8">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f2f63551cdafcdec4169557122522229aa2530e8</a>
+</p>
+
+<p>
+- Work around make changes on modern Mingw to allow release 8.2
+ regression tests to work.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=43a7206fcca3f77503be481565b2a855b9044550">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=43a7206fcca3f77503be481565b2a855b9044550</a>
+</p>
+
+<p>
+Magnus Hagander pushed:
+</p>
+
+<p>
+- Make GUC variables for syslog and SSL always visible. Make the
+ variables visible (but not used) even when support is not compiled in.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4754dbf4c3f857a496b0d29af74786c73d1a8401">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4754dbf4c3f857a496b0d29af74786c73d1a8401</a>
+</p>
+
+<p>
+- Document unavailable parameters in some configurations. Add a note
+ to user-facing parameters that can be removed completely (and not
+ just empty) by #ifdef's depending on build configuration.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8b4d3d44dc7d64aaafd2269d3da8d2873137c691">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8b4d3d44dc7d64aaafd2269d3da8d2873137c691</a>
+</p>
+
+<p>
+- Support for collecting crash dumps on Windows. Add support for
+ collecting "minidump" style crash dumps on Windows, by setting up an
+ exception handling filter. Crash dumps will be generated in
+ PGDATA/crashdumps if the directory is created (the existance of the
+ directory is used as on/off switch for the generation of the dumps).
+ Craig Ringer and Magnus Hagander.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=dcb09b595f88a3bca6097a6acc17bf2ec935d55f">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=dcb09b595f88a3bca6097a6acc17bf2ec935d55f</a>
+</p>
+
+<p>
+- Remove thread dumping constant that requires newer Platform SDK.
+ Since we're not multithreaded it only provides marginally useful
+ information, and it does require a newer version of the Platform SDK
+ than we target. We may want to reconsider this in the future along
+ with a fix for MinGW.
+ <a href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d382828f6ed1edc0f123934d53c52065ecc425c9">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d382828f6ed1edc0f123934d53c52065ecc425c9</a>
+</p>
+
+<h2>Rejected Patches (for now)</h2>
+<p>
+No one was disappointed this week :-)
+</p>
+
+<h2>Pending Patches</h2>
+<p>
+Gurjeet Singh sent in a patch with an improved syntax for adding a
+primary key using an existing index.
+</p>
+
+<p>
+Heikki Linnakangas sent in another revision of the patch to rewrite
+how GiST inserts work.
+</p>
+
+<p>
+Shigeru HANADA sent in two more revisions of the core functionality
+for FOREIGN DATA WRAPPER, part of the SQL/MED specification.
+</p>
+
+<p>
+Marko (johto) Tiikkaja sent in a patch which allows advisory locks to
+be released automatically when the transaction ends.
+</p>
+
+<p>
+ITAGAKI Takahiro sent in a patch to export some functions from copy.c,
+which will be useful for SQL/MED file operations, among other things.
+</p>
+
+<p>
+Florian Pflug sent in another revision of the serializable lock
+consistency patch. Heikki Linnakangas sent in some typo fixes for
+same.
+</p>
+
+<p>
+Florian Pflug sent in two revisions of a fix for the serializable lock
+consistency patch.
+</p>
+
+<p>
+Shigeru HANADA sent in another revision of the patch to implement a
+file foreign data wrapper.
+</p>
+
+<p>
+Shigeru HANADA sent in a patch to use the exported COPY functions in
+the above file_fdw patch.
+</p>
+
+<p>
+Heikki Linnakangas sent in another revision of the patch to fix the
+GiST insert algorithm.
+</p>
+
+<p>
+Alex Hunsaker sent in two revisions of a patch to fix an issue with
+PL/PerlU's treatment of utf8.
+</p>
+
+<p>
+ITAGAKI Takahiro sent in a patch to add pg_read_binary_file().
+</p>
+
+<p>
+Dimitri Fontaine sent in three more revisions of the patch to add
+extensions.
+</p>
+
+<p>
+Magnus Hagander sent in a patch to allow libpq to check its version.
+</p>
+
+<p>
+Peter Eisentraut sent in a patch to fix an issue with localtimestamp
+inside certain queries.
+</p>
+
+<p>
+Pavel Stehule sent in another revision of the patch to add
+FOREACH...IN ARRAY to PL/pgsql.
+</p>
+
+<p>
+Robert Haas sent in a patch to fix an issue with unlogged tables vs.
+xlog.
+</p>
+
+<p>
+Pavel Stehule sent in a patch to factor out some redundant code from
+pl_exec.c.
+</p>
+
+<p>
+Robert Haas sent in another revision of the patch to relax synchronous
+commit behavior when no WAL is written.
+</p>
+
+<p>
+Peter Eisentraut sent in a patch to allow casting a table's row type
+to the table's supertype if it is a typed table.
+</p>
+
+<p>
+Peter Eisentraut sent in a WIP patch which would switch psql from
+normal to expanded and vice versa depending on the width of the
+terminal window it's in.
+</p>
+
+<p>
+Tomas Vondra sent in another revision of the patch to keep a timestamp
+of the last stats reset by database, table and function.
+
+</p>
+