== PostgreSQL Weekly News - September 02 2012 ==

== PostgreSQL Weekly News - September 02 2012 ==

Philly PUG will have its first meeting Sept 12, 2012. Bruce Momjian
presents: What's new in PostgreSQL 9.2. Details and R, SVP, below.
http://www.phlpug.org/events/78529522/

PgDay Argentina 2012, a mini conference focused on connecting bussines
& new users with the PostgreSQL community, will take place November
13th, 2012 in Buenos Aires, Argentina.
http://www.pgday.com.ar/buenosaires2012

This year Ecuador's PGDay will be held at Quito city on November 17th,
2012. The Call for Papers is open until October 10. Send proposals
to Jaime Casanova jaime <AT> 2ndquadrant <DOT> com.

The sixth edition of the Italian PostgreSQL Day (PGDay.IT 2012) will
be held on November 23, 2012 in Prato, Tuscany. The International
Call for Papers is now open. Talks and presentations in English are
accepted. Information in English for papers submission is available
at:
http://2012.pgday.it/call-for-papers/international-call-for-papers/

== PostgreSQL Local ==

PostgreSQL Session will be held on October 4th, 2012, in Paris,
France. More information at:
http://www.postgresql-sessions.org/en/4/

PostgreSQL Conference Europe 2012 will be in Prague, Czech Republic
on October 23-26.
http://2012.pgconf.eu/

PostgreSQL Day Argentina 2012 will be held on November 13th in Bernal,
Buenos Aires, at the National University of Quilmes. It will cover
topics for PostgreSQL users, developers and contributors, as well as
decision and policy makers. For more information about the
conference, please see the website at
http://www.pgday.com.ar/quilmes2012?lang=en

== PostgreSQL in the News ==

Planet PostgreSQL: http://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david(at)fetter(dot)org, German language
to pwn(at)pgug(dot)de, Italian language to pwn(at)itpug(dot)org(dot) Spanish language
to pwn(at)arpug(dot)com(dot)ar(dot)

== Applied Patches ==

Heikki Linnakangas pushed:

- Collect and use histograms of lower and upper bounds for range
types. This enables selectivity estimation of the <<, >>, &<, &>
and && operators, as well as the normal inequality operators: <, <=,
>=, >. "range @> element" is also supported, but the range-variant
@> and <@ operators are not, because they cannot be sensibly
estimated with lower and upper bound histograms alone. We would need
to make some assumption about the lengths of the ranges for that.
Alexander's patch included a separate histogram of lengths for that,
but I left that out of the patch for simplicity. Hopefully that
will be added as a followup patch. The fraction of empty ranges is
also calculated and used in estimation. Alexander Korotkov, heavily
modified by me.
http://git.postgresql.org/pg/commitdiff/918eee0c497c88260a2e107318843c9b1947bc6f

- Optimize SP-GiST insertions. This includes two micro-optimizations
to the tight inner loop in descending the SP-GiST tree: 1. avoid an
extra function call to index_getprocinfo when calling user-defined
choose function, and 2. avoid a useless palloc+pfree when node
labels are not used.
http://git.postgresql.org/pg/commitdiff/c82dedb7a8a953785f24a3b10de376760d60c24c

- Fix division by zero in the new range type histogram creation.
Report and analysis by Matthias.
http://git.postgresql.org/pg/commitdiff/3e6eb0dd0a0982c61420a0d18d3e485bd2c2819c

- Fix typos in README.
http://git.postgresql.org/pg/commitdiff/fe811ae8105a89ea60561dfae2fa7c3504a238a1

Bruce Momjian pushed:

- Have pgindent requre pg_bsd_indent version 1.2 now that a new
version has been created by adding #include <stdlib.h> to parse.c.
Per request from Kevin Grittner.
http://git.postgresql.org/pg/commitdiff/e40bddb0f3ce9f9bf7c960b35f6ac0c19f65612b

- Document the lack of reading the PGDATABASE environment variable in
pg_restore.
http://git.postgresql.org/pg/commitdiff/483c2c1071c45e275782d33d646c3018f02f9f94

- Document how to create advisory lock "bigint" values in SQL. David
E. Wheeler
http://git.postgresql.org/pg/commitdiff/bf849af7f347ebcd394d6d789f557e75ead2f5ee

- Update doc mention of how to compute bigint advisory lock value, per
Tom Lane's correction.
http://git.postgresql.org/pg/commitdiff/5ea6c9d79882815d4cc1c3c302f415eb637466f2

- Prevent psql tab completion in SET from adding TO when the equals
sign has no space before it. Report by Erik Rijkers
http://git.postgresql.org/pg/commitdiff/65b2ee27ad926f622f06c3a4029b621e8d72fb67

- Adjust pg_test_timing to show shortest test durations first, place
percentage column before count column. Docs updated.
http://git.postgresql.org/pg/commitdiff/0f3351aacf5cd5fa87c31fd0d1f7f8dc0409c0b3

- Report postmaster.pid file as empty if it is empty, rather than
reporting in contains invalid data.
http://git.postgresql.org/pg/commitdiff/3825963e7fbaa8dbc462d4f5286ff6149f4703dd

- Document that NOTIFY events are visible to all users.
http://git.postgresql.org/pg/commitdiff/9fe6da5c0d8e70c9a541c3e1e0d637ab19c75ac1

- Remove old documentation warnings about the use of bigint.
http://git.postgresql.org/pg/commitdiff/48a9c7823e032fde54cb0658fbd488809a3fdc69

- Document that log_autovacuum_min_duration can be used to monitor
autovacuum activity. Per report from Marc Mamin
http://git.postgresql.org/pg/commitdiff/83fbfec383d7f7ef1331ba02db3d0fdf50abf112

- Remove configure flag --disable-shared, as it is no longer used by
any port. The last use was QNX, per Peter Eisentraut.
http://git.postgresql.org/pg/commitdiff/381a9ed66d8a601eb972be172e7251ca7f0e9d78

- Document that max_locks_per_transaction might need to be increased
for queries on parent tables, per suggestion from Josh Berkus.
http://git.postgresql.org/pg/commitdiff/39b42ecb059e24bb39a62d91fe57ab7b9ca5a2f5

- Remove doc mention of --enable-shared, per Tom.
http://git.postgresql.org/pg/commitdiff/1fbc30f1dca6624c01a9a6a9ff711a7036c68532

- Revert 1fbc30f1dca6624c01a9a6a9ff711a7036c68532 because the
--enable-shared is about Plyton's configure, not ours.
http://git.postgresql.org/pg/commitdiff/39d0653d058b87b437be05fd295ceb5bb4e9e05c

- Properly document that SIGTERM is OK for users to use on a postgres
session, now that pg_terminate_backend() uses it. Josh Kupershmidt
http://git.postgresql.org/pg/commitdiff/b5dc7612a5f66a08c6d46656d359fc1c69670f36

- Clarify FreeBSD instructions in pg_test_timing. Josh Kupershmidt
http://git.postgresql.org/pg/commitdiff/c36b06a70d303c738f092f264585f621b6b30b29

- Add Perl emacs formatting macros to src/tools/editors/emacs.samples.
Peter Eisentraut
http://git.postgresql.org/pg/commitdiff/5fcb58baca7a78e688b84275958c450670ba62a8

- In pg_upgade, document that the port numbers must be different when
checking an old running server.
http://git.postgresql.org/pg/commitdiff/f789909b59c59a33e34feac3bed2c86f18159122

- Revert doc patch 305557984dd964ac397c6752e9d0f14646b60f15 as the
values are sometimes signed, sometimes unsigned.
http://git.postgresql.org/pg/commitdiff/53fa0c6db8e9ebbef9a2806193797735998520c6

- Add small doc mention that libpq is named after POSTQUEL.
http://git.postgresql.org/pg/commitdiff/6c82a86c6f11815df371a310e3734030b1a635f4

- Update URLs that pointed to sun.com; either repoint them or remove
them.
http://git.postgresql.org/pg/commitdiff/7682c5947dff4368753890935522dedfb93e1c78

Tom Lane pushed:

- Fix DROP INDEX CONCURRENTLY IF EXISTS. This threw ERROR, not the
expected NOTICE, if the index didn't exist. The bug was actually
visible in not-as-expected regression test output, so somebody
wasn't paying too close attention in commit
8cb53654dbdb4c386369eb988062d0bbb6de725e. Per report from Brendan
Byrd.
http://git.postgresql.org/pg/commitdiff/e323c553017601597b6a5f9f19426587df512ad9

- Add section IDs to subsections of syntax.sgml that lacked them.
This is so that these sections will have stable HTML tags that one
can link to, rather than things like "AEN1902". Perhaps we should
mount a campaign to do this everywhere, but I've found myself
pointing at syntax.sgml subsections often enough to be sure it's
useful here.
http://git.postgresql.org/pg/commitdiff/87703287849bf785400d0daf57b9d6b5a05d0780

- Improve a couple of 9.2 release note entries. Clarify the
compatibility notes about EXTRACT() and about statistics timing
columns.
http://git.postgresql.org/pg/commitdiff/7417a8e3dd14886887447053a5ccbd4f9501ba61

- Remove hstore--1.0.sql. Since we're not installing this file
anymore, it has no reason to exist, other than as historical
reference; but we have an SCM for that.
http://git.postgresql.org/pg/commitdiff/9db098dfa91906cee4fffc1e3ba8ba3899820d5f

- Remove pg_stat_statements--1.0.sql, too. Per Peter Geoghegan.
http://git.postgresql.org/pg/commitdiff/0a83f2492f38fd0b82452dfd2a80cc70486ba73d

- Adjust definition of cheapest_total_path to work better with
LATERAL. In the initial cut at LATERAL, I kept the rule that
cheapest_total_path was always unparameterized, which meant it had
to be NULL if the relation has no unparameterized paths. It turns
out to work much more nicely if we always have *some* path nominated
as cheapest-total for each relation. In particular, let's still say
it's the cheapest unparameterized path if there is one; if not, take
the cheapest-total-cost path among those of the minimum available
parameterization. (The first rule is actually a special case of the
second.) This allows reversion of some temporary lobotomizations I'd
put in place. In particular, the planner can now consider hash and
merge joins for joins below a parameter-supplying nestloop, even if
there aren't any unparameterized paths available. This should bring
planning of LATERAL-containing queries to the same level as queries
not using that feature. Along the way, simplify management of
parameterized paths in add_path() and friends. In the original
coding for parameterized paths in 9.2, I tried to minimize the logic
changes in add_path(), so it just treated parameterization as yet
another dimension of comparison for paths. We later made it ignore
pathkeys (sort ordering) of parameterized paths, on the grounds that
ordering isn't a useful property for the path on the inside of a
nestloop, so we might as well get rid of useless parameterized paths
as quickly as possible. But we didn't take that reasoning as far as
we should have. Startup cost isn't a useful property inside a
nestloop either, so add_path() ought to discount startup cost of
parameterized paths as well. Having done that, the secondary
sorting I'd implemented (in add_parameterized_path) is no longer
needed --- any parameterized path that survives add_path() at all is
worth considering at higher levels. So this should be a bit faster
as well as simpler.
http://git.postgresql.org/pg/commitdiff/e83bb10d6dcf05a666d4ada00d9788c7974ad378

- Improve EXPLAIN's ability to cope with LATERAL references in plans.
push_child_plan/pop_child_plan didn't bother to adjust the
"ancestors" list of parent plan nodes when descending to a child
plan node. I think this was okay when it was written, but it's not
okay in the presence of LATERAL references, since a subplan node
could easily be returning a LATERAL value back up to the same
nestloop node that provides the value. Per changed regression test
results, the omission led to failure to interpret Param nodes that
have perfectly good interpretations.
http://git.postgresql.org/pg/commitdiff/d1a4db8d25ec53fd17e99168bc5efa0b16ef6fed

- Suppress creation of backwardly-indexed paths for LATERAL join
clauses. Given a query such as SELECT * FROM foo JOIN LATERAL
(SELECT foo.var1) ss(x) ON ss.x = foo.var2 the existence of the join
clause "ss.x = foo.var2" encourages indxpath.c to build a
parameterized path for foo using any index available for foo.var2.
This is completely useless activity, though, since foo has got to be
on the outside not the inside of any nestloop join with ss. It's
reasonably inexpensive to add tests that prevent creation of such
paths, so let's do that.
http://git.postgresql.org/pg/commitdiff/77387f0ac859c099c6ab669db1e7a852524696c4

- Improve coding of gistchoose and gistRelocateBuildBuffersOnSplit.
This is mostly cosmetic, but it does eliminate a speculative
portability issue. The previous coding ignored the fact that
sum_grow could easily overflow (in fact, it could be summing
multiple IEEE float infinities). On a platform where that didn't
guarantee to produce a positive result, the code would misbehave.
In any case, it was less than readable.
http://git.postgresql.org/pg/commitdiff/e5db11c5582b469c04a11f217a0f32c827da5dd7

- Make configure probe for mbstowcs_l as well as wcstombs_l. We
previously supposed that any given platform would supply both or
neither of these functions, so that one configure test would be
sufficient. It now appears that at least on AIX this is not the
case ... which is likely an AIX bug, but nonetheless we need to cope
with it. So use separate tests. Per bug #6758; thanks to Andrew
Hastie for doing the followup testing needed to confirm what was
happening. Backpatch to 9.1, where we began using these functions.
http://git.postgresql.org/pg/commitdiff/58a031f920c225b20fdb45c1e56fe41ed7568900

- Fix LATERAL references to join alias variables. I had thought this
case worked already, but perhaps I didn't re-test it after adding
extract_lateral_references() ...
http://git.postgresql.org/pg/commitdiff/da3df998702061b4b63d83d5354b148e812f21f8

- Partially restore qual scope checks in distribute_qual_to_rels().
The LATERAL implementation is now basically complete, and I still
don't see a cost-effective way to make an exact qual scope
cross-check in the presence of LATERAL. However, I did add a
PlannerInfo.hasLateralRTEs flag along the way, so it's easy to make
the check only when not hasLateralRTEs. That seems to still be
useful, and it beats having no check at all.
http://git.postgresql.org/pg/commitdiff/c97a547a4a0913e37e5dd1f026ac3c281326b215

- More documentation updates for LATERAL. Extend xfunc.sgml's
discussion of set-returning functions to show an example of using
LATERAL, and recommend that over putting SRFs in the targetlist. In
passing, reword func.sgml's section on set-returning functions so
that it doesn't claim that the functions listed therein are all the
built-in set-returning functions. That hasn't been true for a long
time, and trying to make it so doesn't seem like it would be an
improvement. (Perhaps we should rename that section?) Both per
suggestions from Merlin Moncure.
http://git.postgresql.org/pg/commitdiff/06310178ef54720bc4ed7bc85c887e6ebed24d83

- Fix broken link in installation.sgml. Linking to other parts of the
manual doesn't work when building the standalone INSTALL document.
http://git.postgresql.org/pg/commitdiff/b8a4093b5890aa774ae90bbf44515750aa0ae85c

- Fix mark_placeholder_maybe_needed to handle LATERAL references. If
a PlaceHolderVar contains a pulled-up LATERAL reference, its minimum
possible evaluation level might be higher in the join tree than its
original syntactic location. That in turn affects the ph_needed
level for any contained PlaceHolderVars (that is, those PHVs had
better propagate up the join tree at least to the evaluation level
of the outer PHV). We got this mostly right, but
mark_placeholder_maybe_needed() failed to account for the effect,
and in consequence could leave the inner PHVs with ph_may_need less
than what their ultimate ph_needed value will be. That's bad
because it could lead to failure to select a join order that will
allow evaluation of the inner PHV at a valid location. Fix that,
and add an Assert that checks that we don't ever set ph_needed to
more than ph_may_need.
http://git.postgresql.org/pg/commitdiff/4da6439bd8553059766011e2a42c6e39df08717f

- Drop cheap-startup-cost paths during add_path() if we don't need
them. We can detect whether the planner top level is going to care
at all about cheap startup cost (it will only do so if
query_planner's tuple_fraction argument is greater than zero). If
it isn't, we might as well discard paths immediately whose only
advantage over others is cheap startup cost. This turns out to get
rid of quite a lot of paths in complex queries --- I saw planner
runtime reduction of more than a third on one large query. Since
add_path isn't currently passed the PlannerInfo "root", the easiest
way to tell it whether to do this was to add a bool flag to
RelOptInfo. That's a bit redundant, since all relations in a given
query level will have the same setting. But in the future it's
possible that we'd refine the control decision to work on a
per-relation basis, so this seems like a good arrangement anyway.
Per my suggestion of a few months ago.
http://git.postgresql.org/pg/commitdiff/6d2c8c0e2afa8cbaf99555a24336e93118fd181e

Alvaro Herrera pushed:

- Fix thinko in comment It was confusing symlinks with hard links.
http://git.postgresql.org/pg/commitdiff/34c02044ed7e7defde5a853b26dcd806c872d974

- Remove analyze_new_cluster.sh on make clean, too
http://git.postgresql.org/pg/commitdiff/ab577e63faf792593ca728625a8ef0b1dfaf7500

- pg_upgrade: Fix exec_prog API to be less flaky. The previous
signature made it very easy to pass something other than the
printf-format specifier in the corresponding position, without any
warning from the compiler. While at it, move some of the escaping,
redirecting and quoting responsibilities from the callers into
exec_prog() itself. This makes the callsites cleaner.
http://git.postgresql.org/pg/commitdiff/088c065ce8e405fafbfa966937184ece9defcf20

- syncrep.h must include xlogdefs.h
http://git.postgresql.org/pg/commitdiff/095e6c5a7da10db77d0e43e413fca64c946ad370

- add #includes to plpy_subxactobject.h to make it compile standalone
http://git.postgresql.org/pg/commitdiff/0a664ec27f3937c0ce428c07a41b6d8c7526ec57

- Split resowner.h. This lets files that are mere users of
ResourceOwner not automatically include the headers for stuff that
is managed by the resowner mechanism.
http://git.postgresql.org/pg/commitdiff/45326c5a11530cff5db99c6d4b393439cc901f26

- Split heapam_xlog.h from heapam.h. The heapam XLog functions are
used by other modules, not all of which are interested in the rest
of the heapam API. With this, we let them get just the XLog stuff
in which they are interested and not pollute them with unrelated
includes. Also, since heapam.h no longer requires xlog.h, many
files that do include heapam.h no longer get xlog.h automatically,
including a few headers. This is useful because heapam.h is getting
pulled in by execnodes.h, which is in turn included by a lot of
files.
http://git.postgresql.org/pg/commitdiff/21c09e99dc252269360bd146afee9481fa80abbc

- remove catcache.h from syscache.h. Instead, place a forward struct
declaration for struct catclist in syscache.h. This reduces header
proliferation somewhat.
http://git.postgresql.org/pg/commitdiff/fda0594fc2f4c98ee50ea02fa196ca51db81ea70

- Fix assorted compilation failures in contrib. Evidently I failed to
test a compile after my earlier header shuffling.
http://git.postgresql.org/pg/commitdiff/9df55c8c3f0eba77de57006999d5700292fa9d33

- Split tuple struct defs from htup.h to htup_details.h. This reduces
unnecessary exposure of other headers through htup.h, which is very
widely included by many files. I have chosen to move the function
prototypes to the new file as well, because that means htup.h no
longer needs to include tupdesc.h. In itself this doesn't have much
effect in indirect inclusion of tupdesc.h throughout the tree,
because it's also required by execnodes.h; but it's something to
explore in the future, and it seemed best to do the htup.h change
now while I'm busy with it.
http://git.postgresql.org/pg/commitdiff/c219d9b0a55bcdf81b00da6bad24ac2bf3e53d20

Robert Haas pushed:

- Back-patch fixes for some issues in our Windows socket code into
9.1. This is a backport of commit b85427f2276d02756b558c0024949305ea65aca5.
Per discussion of bug #4958. Some of these fixes probably need to
be back-patched further, but I'm just doing this much for now.
http://git.postgresql.org/pg/commitdiff/ed597d0c322dd42c362701125d4ff55eb7b675f5

- Document that xslt-related RPMs may be needed to build docs.
http://git.postgresql.org/pg/commitdiff/152525b5f3db9b7b58fa06e5d03725288f054b1d

- Comment fixes. Jeff Davis, somewhat edited by me
http://git.postgresql.org/pg/commitdiff/e1a6375d8f3a11f3447bea10883a4cbe1c5d3ec9

- Fix logic bug in gistchoose and gistRelocateBuildBuffersOnSplit.
Every time the best-tuple-found-so-far changes, we need to reset all
the penalty values in which_grow[] to the penalties for the new best
tuple. The old code failed to do this, resulting in inferior index
quality. The original patch from Alexander Korotkov was just two
lines; I took the liberty of fleshing that out by adding a bunch of
comments that I hope will make this logic easier for others to
understand than it was for me.
http://git.postgresql.org/pg/commitdiff/c8ba697a4bdb934f0c51424c654e8db6133ea255

- Document that COPY OUT requires an absolute pathname. As suggested
by Etsuro Fujita, but with somewhat different wording.
http://git.postgresql.org/pg/commitdiff/b9ea8d20fde981997425ba72de7aa23e319e753e

- Add missing period to detail message. Per note from Peter
Eisentraut.
http://git.postgresql.org/pg/commitdiff/a66fca3f0c8899ad360f0300d45cb1b7ac60a17f

- Document how to prevent PostgreSQL itself from exhausting memory.
The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it. Per discussion with
Craig Ringer and Kevin Grittner.
http://git.postgresql.org/pg/commitdiff/35738b5906bb80bc4bb77ce1adea7dfbd3f64274

- Fix checkpoint_timeout documentation to reflect current behavior.
Jeff Janes
http://git.postgresql.org/pg/commitdiff/9bedfbd02b48096f435c5b111591d4e5b717e547

- Cross-link to doc build requirements from install requirements.
Jeff Janes
http://git.postgresql.org/pg/commitdiff/e8d6c98c2f082bead1202b23e9d70e0fbde49129

Peter Eisentraut pushed:

- Small punctuation fixes
http://git.postgresql.org/pg/commitdiff/a5727888d744d1b41bba4d84dadf9e5c519aab45

- Add strerror() string to chdir() error message
http://git.postgresql.org/pg/commitdiff/1a26e1c766fa84c2f93473eed83f0133d4b2ac5f

- Also check for Python platform-specific include directory Python can
be built to have two separate include directories: one for
platform-independent files and one for platform-specific files. So
far, this has apparently never mattered for a PL/Python build. But
with the new multi-arch Python packages in Debian and Ubuntu, this
is becoming the standard configuration on these platforms, so we
must check these directories separately to be able to build there.
Also add a bit of reporting in configure to be able to see better
what is going on with this.
http://git.postgresql.org/pg/commitdiff/9cffb187d80d87399c5d2c4577b3f3ba775ef028

- psql: Reduce compatibility warning. Only warn when connecting to a
newer server, since connecting to older servers works pretty well
nowadays. Also update the documentation a little about current
psql/server compatibility expectations.
http://git.postgresql.org/pg/commitdiff/5cad02452457d7f6f29404411dfe13e6fe8accb7

Andrew Dunstan pushed:

- Restore setting of _USE_32BIT_TIME_T to 32 bit MSVC builds. This
was removed in commit cd004067742ee16ee63e55abfb4acbd5f09fbaab,
we're not quite sure why, but there have been reports of crashes due
to Alexander Shulgin Perl being built with it when we are not, and
it certainly seems like the right thing to do. There is still some
uncertainty as to why it sometimes fails and sometimes doesn't.
Original patch from Owais Khani, substantially reworked and extended
by Andrew Dunstan.
http://git.postgresql.org/pg/commitdiff/ef58b87df2afe91189e9ffb81b65c1127d53bc88

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Dickson S. Guedes sent in another revision of the patch to add IF NOT
EXISTS to CREATE SCHEMA.

Amit Kapila sent in another revision of the patch to improve performance
by reducing WAL for update operations.

Alvaro Herrera sent in two more revisions of the patch to add foreign
key locks.

Dimitri Fontaine sent in a patch tweaking the behavior of EVENT
triggers.

Dean Rasheed sent in three more revisions of the patch to implement
updatable views.

Tom Lane sent in a patch to fix an issue where function parameters
aren't getting to the functions they are part of because of the lack
of type inference.

Amit Kapila sent in a patch to document pg_resetxlog and compute the
max LSN of data pages.

Owais Khan and Andrew Dunstan traded patches to use a 32-bit time_t
structure on Windows in order not to break PL/Perl.

Dimitri Fontaine sent in a patch to prevent event triggers from firing
in stand-alone mode.

Peter Eisentraut sent in a patch to change the many "%d tuples done"
lines to a sort of progress counter that stays on the same line.

Pavel Stehule sent in another revision of the patch to allow tuning
the display of booleans in psql.

Bruce Momjian and Tom Lane traded patches to make a pg_upgrade failure
mode involving socket directories less likely.

KaiGai Kohei sent in a patch to fix a case sepgsql missed in CREATE
TABLE AS.

KaiGai Kohei sent in a patch to make sepgsql follow recent changes to
the core API.

Tomas Vondra sent in two more revisions of the patch to enable pgbench
to write random samples into the transaction log.

Andrew Dunstan sent in a patch to make pg_upgrade work on Windows.

Andrew Dunstan sent in a patch to make pg_upgrade's "make check" work
on Windows with Mingw.

Tom Lane sent in a proof-of-concept patch for talking to a standalone
backend using libpq and a pair of pipes.