David Fetter | 28 Jul 07:41 2014

== PostgreSQL Weekly News - July 27 2014 ==

== PostgreSQL Weekly News - July 27 2014 ==

PostgreSQL 9.4 Beta 2 released.  TEST!
http://www.postgresql.org/about/news/1533/

PostgreSQL bug fix versions 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22
out now; 8.4 is now EOL.
Upgrade ASAP!
http://www.postgresql.org/about/news/1534/

== PostgreSQL Product News ==

Bi-Direction Replication (BDR), an asynchronous multi-master
replication system for PostgreSQL, has been announced by 2ndQuadrant.
http://www.2ndQuadrant.com/bdr

pgAdmin3 v1.20.0 Beta 1, a multi-platform stand-alone GUI
administration tool, released.
http://www.pgadmin.org/development/changelog.php

== PostgreSQL Jobs for July ==

http://archives.postgresql.org/pgsql-jobs/2014-07/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
(Continue reading)

Guillaume Lelarge | 25 Jul 09:25 2014

pgAdmin v.1.20.0 Beta 1 now available

pgAdmin v1.20.0 Beta 1 is now available for testing in source from:

http://www.postgresql.org/ftp/pgadmin3/release/v1.20.0-beta1/

Unfortunately, Windows and Mac OS X distributions aren't yet available. Nevertheless, you can still have it with the PostgreSQL 9.4 beta 2 one-click installer from:

http://www.postgresql.org/download/snapshots/

We're still working on a visual tour. In the meantime, the list of new features is available in the changelog (http://www.pgadmin.org/development/changelog.php).

Please download a copy to test, and report any issues to pgadmin-support(at)postgresql(dot)org to help us prepare for our upcoming 1.20 final release.

Regards.


--
Magnus Hagander | 24 Jul 12:54 2014

2014-07-24: PostgreSQL updates 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22 released

The PostgreSQL Global Development Group has released an update to all
supported version of the database system, including versions 9.3.5,
9.2.9, 9.1.14, 9.0.18, and 8.4.22. This minor release fixes a number
of issues discovered and reported by users over the last four months,
including some data corruption issues, and is the last update of
version 8.4.  Users of version 9.3 will want to update at the earliest
opportunity; users of version 8.4 will want to schedule an upgrade to
a supported PostgreSQL version.

Among the notable issues fixed in this release are:

PostgreSQL 9.3 and pg_upgrade
-----------------------------
Users who upgraded to version 9.3 using pg_upgrade may have an issue
with transaction information which causes VACUUM to eventually
fail. These users should run the script provided in the release notes
to determine if their installation is affected, and then take the
remedy steps outlined there.

PostgreSQL 9.3 crash recovery
-----------------------------
Three issues which could compromise data integrity during crash
recovery on master or standby servers in PostgreSQL 9.3 have been
fixed.

GIN and GiST indexes
--------------------

Three issues with GIN and GiST indexes, used for PostGIS and full text
indexing, can cause corruption or incorrect query responses.  Any
indexes on bit or bit varying columns should be rebuilt following the
instructions in the release notes.

Security during make check
--------------------------
The insecure socket permissions during "make check", reported in a
previous security announcement, have now been fixed.

With this release, *version 8.4 is now End-of-Life (EOL)*, per our
Versioning Policy (http://www.postgresql.org/support/versioning/).
This means that no additional updates will be released for version
8.4, and users should plan to upgrade to a later version very soon.

In addition the above, this update release includes the following
fixes which affect multiple PostgreSQL versions:

* Fix race condition with concurrent tuple updating
* Prevent "could not find pathkey item to sort" planner error
* Properly optimize subqueries with set-returning functions
* Repair planner regression in optimizing AND/OR NULL
* Fix planner handling of VARIADIC functions
* Make json_populate_recordset handle nested JSON properly
* Prevent corruption of TOAST values when creating complex types
* Prevent "record type has not been registered" query error
* Fix a possible crash condition with functions and rewinding cursors
* Patch three memory leaks
* Fix row checks for rows deleted by subtransactions
* Change how pg_stat_activity displays sessions during PREPARE 
TRANSACTION
* Prevent multixact ID corruption during VACUUM FULL
* Fix indentation when displaying complex view definitions
* Fix client hostname lookup in pg_hba.conf
* Fix libpython linking on OSX
* Avoid buffer bloat in libpq
* Fix an issue with dumping materialized views
* Fix pg_upgrade's handling of multixact IDs
* Make sure that pgcrypto clears sensitive information from memory
* Time zone updates for Crimea, Egypt, and Morocco

Four Windows-specific fixes are included in this release:

* Prevent tablespace creation recovery errors
* Fix detection of socket failures
* Allow users to change parameters after startup
* Properly quote executable names so they don't fail

A few of the issues above require post-update steps to be carried out
by affected users.  Please see the release notes for details.

As with other minor releases, users are not required to dump and
reload their database or use pg_upgrade in order to apply this update
release; you may simply shut down PostgreSQL and update its binaries.
Users who have skipped multiple update releases may need to perform
additional post-update steps; see the Release Notes for details.

Links:
   Download updates: http://www.postgresql.org/download
   Release notes: 
http://www.postgresql.org/docs/current/static/release.html

--
  Magnus Hagander
  PostgreSQL Core Team
  http://www.postgresql.org

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Magnus Hagander | 24 Jul 12:48 2014

PostgreSQL 9.4 Beta 2 Released

The PostgreSQL Global Development Group has made available the second
beta release of PostgreSQL 9.4.  This beta contains previews of all of
the features which will be available in version 9.4, plus corrections
for many of the issues discovered by users who tested 9.4 Beta 1.
Please download, test, and report what you find.

Among the changes made since 9.4 Beta 1 are:

* Fix handling of two-phase commit and prepared statements for logical 
decoding
* Multiple fixes for bugs in pg_recvlogical
* Change slot handling logic for replication slots
* Add support for BSD and e2fsprogs UUID libraries.
* Multiple jsonb bug fixes
* Remove use_json_as_text options from json functions
* Make json_build_* functions STABLE instead of IMMUTABLE
* Prevent ALTER SYSTEM from changing the data directory
* Prevent autovacuum-related crash
* Many documentation improvements and changes

Beta 2 includes changes to pg_control and to the system catalogs.  As
such, users who have been testing Beta 1 will need to upgrade in order
to test Beta 2.  We suggest using pg_upgrade for this upgrade in order
to test that as well.

For a full listing of the features in version 9.4 Beta, please see the
release notes: 
http://www.postgresql.org/docs/9.4/static/release-9-4.html.
Additional descriptions and notes on the new features are available on
the 9.4 Features Wiki Page:
http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.4.

We depend on our community to help test the next version in order to
guarantee that it is high-performance and bug-free.  Please download
PostgreSQL 9.4 Beta 2 and try it with your workloads and applications
as soon as you can, and give feedback to the PostgreSQL developers.
Features and APIs in Beta 2 will not change substantially before final
release, so it is now safe to start building applications against the
new features. More information on how to test and report issues:
http://www.postgresql.org/developer/beta

Get the PostgreSQL 9.4 Beta 2, including binaries and installers for
Windows, Linux and Mac from our download page:
http://www.postgresql.org/download.

Full documentation of the new version is available online:
http://www.postgresql.org/docs/9.4/static, and also installs with
PostgreSQL.

--
  Magnus Hagander
  PostgreSQL Core Team
  http://www.postgresql.org

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Guillaume Lelarge | 21 Jul 19:51 2014

Call for papers - PGConf.EU 2014 - extended till 07/24!

The Call for Papers deadline for pgconf.eu 2014 has been extended. Instead of ending tomorrow, the new deadline is *Thursday, July 24th, midnight CET*.

However, we'll start approving talks that have already been submitted as soon as possible. So, make sure you submit really soon.

PostgreSQL Conference Europe 2014 will be held on October 21-24 in the Hotel Miguel Angel in Madrid, Spain. 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://2014.pgconf.eu/.

We are now accepting proposals for talks, in english or spanish. If you are submitting a talk in Spanish, please write a short summary of the abstract in English in
the "submission notes" field.

Each session will last 45 minutes, and may be on any topic related to PostgreSQL. Suggested topic areas include:

* Developing applications for PostgreSQL
* Administering large scale PostgreSQL installations
* Case studies and/or success stories of PostgreSQL deployments
* PostgreSQL tools and utilities
* PostgreSQL hacking
* Community & user groups
* Tuning the server
* Migrating from other systems
* Scaling/replication
* Benchmarking & hardware
* PostgreSQL related products

Of course, we're happy to receive proposals for talks on other PostgreSQL related topics as well.

We may also have a limited number of longer, 90-minute, slots available. Please indicate clearly in your submission if you wish to make a 90-minute talk.

Finally, there will be a session of five minute lightning talks. A separate call for proposals will be made for them further on.

The submission deadline is July 24th. Selected speakers will be notified before August 12th, 2013.

Please submit your proposals by going to http://2014.pgconf.eu/callforpapers/ and following the instructions there.

The proposals will be considered by committee who will produce a schedule to be published nearer the conference date.

All selected speakers will get free entry to the conference (excluding training sessions). We do not in general cover travel and accommodations for speakers, but may be able to do that in limited cases. If you require assistance with funding to be able to attend, please make a note of this in the submission notes field.

This call for papers is also available on the web at http://2014.pgconf.eu/callforpapers/

We look forward to hearing from you, and seeing you in Madrid in October!


--
David Fetter | 21 Jul 06:08 2014

== PostgreSQL Weekly News - July 20 2014 ==

== PostgreSQL Weekly News - July 20 2014 ==

The start of pgMKE will be August 5, 2014 in Milwaukee, WI, USA.
RSVP to help ensure the right amount of pizza.
https://plus.google.com/events/c7iba3eh9366v3hki7etcbj2074

== PostgreSQL Jobs for July ==

http://archives.postgresql.org/pgsql-jobs/2014-07/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.  Send talk proposals to ecpug AT postgresql DOT org.

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-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.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Fujii Masao pushed:

- Remove incorrect comment from postgres_fdw.c.  Etsuro Fujita
  http://git.postgresql.org/pg/commitdiff/ab774859456eb441ef049bf66af38b259cbdacce

- Prevent bitmap heap scans from showing unnecessary block info in
  EXPLAIN ANALYZE.  EXPLAIN ANALYZE shows the information of the
  numbers of exact/lossy blocks which bitmap heap scan processes. But,
  previously, when those numbers were both zero, it displayed only the
  prefix "Heap Blocks:" in TEXT output format.  This is strange and
  would confuse the users. So this commit suppresses such unnecessary
  information.  Backpatch to 9.4 where EXPLAIN ANALYZE was changed so
  that such information was displayed.  Etsuro Fujita
  http://git.postgresql.org/pg/commitdiff/d4635b16fe3d0fae65d7735d9e926a1b20a90781

Noah Misch pushed:

- MSVC: Apply icons to all binaries having them in a MinGW build.
  http://git.postgresql.org/pg/commitdiff/c4a448eb55f35a7f582e30d15ee0ea10b67b70a2

- MSVC: Process Makefile line continuations more like "make" does.
  Unlike "make" itself, the MSVC build process recognized a
  continuation even with whitespace after the backslash.  (Due to a
  typo, some code sites accepted the letter "s" instead of
  whitespace).  Also, it would consume any number of newlines
  following a single backslash.  This is mere cleanup; those behaviors
  were unlikely to cause bugs.
  http://git.postgresql.org/pg/commitdiff/35d19a9a37c245ff7c640743f37b8df227fd24dc

- MSVC: Recognize PGFILEDESC in contrib and conversion_procs modules.
  Achieve this by consistently using four-argument
  Solution::AddProject() calls.  Remove ad hoc Makefile parsing made
  redundant by doing that.  Michael Paquier and Noah Misch, reviewed
  by MauMau.
  http://git.postgresql.org/pg/commitdiff/91f03ba5cf88b393bf2509f3f00dd00437a5bd54

- Add file version information to most installed Windows binaries.
  Prominent binaries already had this metadata.  A handful of minor
  binaries, such as pg_regress.exe, still lack it; efforts to
  eliminate such exceptions are welcome.  Michael Paquier, reviewed by
  MauMau.
  http://git.postgresql.org/pg/commitdiff/0ffc201a51395ca71fe429ef86c872850a5850ee

- Fix warnings added in 8d9a0e85bd6ab4fe5268a1d759a787f72ff9333e.
  http://git.postgresql.org/pg/commitdiff/52be3aae5bfe84346b7ce202eae3447a07dfc882

- contrib/test_decoding/Makefile sets MODULES, so omit OBJS.  Michael
  Paquier
  http://git.postgresql.org/pg/commitdiff/c0e8fb6148ce9c539f6fbde71faa955cab85f214

- Limit pg_upgrade authentication advice to always-secure techniques.
  ~/.pgpass is a sound choice everywhere, and "peer" authentication is
  safe on every platform it supports.  Cease to recommend "trust"
  authentication, the safety of which is deeply
  configuration-specific.  Back-patch to 9.0, where pg_upgrade was
  introduced.
  http://git.postgresql.org/pg/commitdiff/85f95739ec0c2d9c6afb10d9a0b42732191fbbde

Peter Eisentraut pushed:

- doc: small fixes for REINDEX reference page From: Josh Kupershmidt
  <schmiddy <at> gmail.com>
  http://git.postgresql.org/pg/commitdiff/f162fb75b329bc5370b3ece59f5ef0d5ba0f15d6

- Add missing serial commas.  Also update one place where the
  wal_level "logical" was not added to an error message.
  http://git.postgresql.org/pg/commitdiff/d38228fe4029cce3af396bf5b1728d8000ab32c8

- Small spelling fix
  http://git.postgresql.org/pg/commitdiff/d90ad5d8abe7947520686239a7547f2eb8cc9a8d

- Add missing source files to nls.mk.  These are files under common/
  that have been moved around.  Updating these manually is not
  satisfactory, but it's the only solution at the moment.
  http://git.postgresql.org/pg/commitdiff/f9ddcf75430467493aa6c2b07a45776e4ae8b416

- doc: Put new options in right order on reference pages
  http://git.postgresql.org/pg/commitdiff/9a218c02b8f10bc5aa3a9227b0a30ad0b6bdf6a6

- pg_basebackup: Add more information about --max-rate option to help
  output.  It was previously not clear what unit the option argument
  should have.
  http://git.postgresql.org/pg/commitdiff/e806da6bdbe9544e061b635f33b8ee561094b4d0

- pg_upgrade: Fix spacing in help output
  http://git.postgresql.org/pg/commitdiff/e0da6ec618a3890d7d5d8b8342645e6683848d67

- doc: Spell checking
  http://git.postgresql.org/pg/commitdiff/aa688725615a4fb55c460f072fb144900a59582d

- Replace "internationalize" with "localize" where appropriate
  http://git.postgresql.org/pg/commitdiff/2ee4efc4081e0487d70607ca0d0d4abdbb85106f

Magnus Hagander pushed:

- Remove dependency on wsock32.lib in favor of ws2_32.  ws2_32 is the
  new version of the library that should be used, as it contains the
  require functionality from wsock32 as well as some more (which is
  why some binaries were already using ws2_32).  Michael Paquier,
  reviewed by MauMau
  http://git.postgresql.org/pg/commitdiff/a16bac36eca8158cbf78987e95376f610095f792

- Include SSL compression status in psql banner and connection
  logging.  Both the psql banner and the connection logging already
  included SSL status, cipher and bitlength, this adds the information
  about compression being on or off.
  http://git.postgresql.org/pg/commitdiff/c93bf8c6ccf7ef1cec6b01fec1888f84831295ee

- Detect presence of SSL_get_current_compression.  Apparently we still
  build against OpenSSL so old that it doesn't have this function, so
  add an autoconf check for it to make the buildfarm happy. If the
  function doesn't exist, always return that compression is disabled,
  since presumably the actual compression functionality is always
  missing.  For now, hardcode the function as present on MSVC, since
  we should hopefully be well beyond those old versions on that
  platform.
  http://git.postgresql.org/pg/commitdiff/c9e1ad7faf75aeda633e27ba6c042dabe4aa353d

- Move check for SSL_get_current_compression to run on mingw.  Mingw
  uses a different header file than msvc, so we don't get the
  hardcoded value, so we need the configure test to run.
  http://git.postgresql.org/pg/commitdiff/5571caf42d62ea30c452b0ae5f1748289ae613b4

- Add option to pg_ctl to choose event source for logging.  pg_ctl
  will log to the Windows event log when it is running as a service,
  which is the primary way of running PostgreSQL on Windows. This
  option makes it possible to specify which event source to use for
  this, in order to separate different instances. The server logging
  itself is still controlled by the regular logging parameters,
  including a separate setting for the event source. The parameter to
  pg_ctl only controlls the logging from pg_ctl itself.  MauMau,
  review in many iterations by Amit Kapila and me.
  http://git.postgresql.org/pg/commitdiff/c0e4520b1667279389bb0dce8d867df2ac25042a

- Revert broken change to pgevent.c.  pgevent doesn't include the
  global PostgreSQL headers, for a reason, and therefor cannot rely on
  defines in it...
  http://git.postgresql.org/pg/commitdiff/6cd471a6d46b463e5222e5bb2d859311ddc1d86a

Alvaro Herrera pushed:

- psql: Show tablespace size in \db+.  Fabrízio de Royes Mello
  http://git.postgresql.org/pg/commitdiff/ee80f043bc9b92dbbb1ff9577c3c601746124092

- Move view reloptions into their own varlena struct.  Per discussion
  after a gripe from me in
  http://www.postgresql.org/message-id/20140611194633.GH18688 <at> eldon.alvh.no-ip.org
  Jaime Casanova
  http://git.postgresql.org/pg/commitdiff/346d7be184a617ca9f64bdf5c25fd6bcd5231293

- Fix REASSIGN OWNED for text search objects.  Trying to reassign
  objects owned by a user that had text search dictionaries or
  configurations used to fail with: ERROR:  unexpected classid 3600 or
  ERROR:  unexpected classid 3602 Fix by adding cases for those object
  types in a switch in pg_shdepend.c.  Both REASSIGN OWNED and text
  search objects go back all the way to 8.1, so backpatch to all
  supported branches.  In 9.3 the alter-owner code was made generic,
  so the required change in recent branches is pretty simple; however,
  for 9.2 and older ones we need some additional reshuffling to enable
  specifying objects by OID rather than name.  Text search templates
  and parsers are not owned objects, so there's no change required for
  them.  Per bug #9749 reported by Michal Novotný
  http://git.postgresql.org/pg/commitdiff/6bdf4b9c7dde84902a0cc19c27c51c016485b8e6

- Add missing doc changes for ee80f043bc9b.  Per note from Tom Lane
  http://git.postgresql.org/pg/commitdiff/da6ac4a6683788ed7042a46568f2b040210830f8

Andrew Dunstan pushed:

- json_build_object and json_build_array are stable, not immutable.
  These functions indirectly invoke output functions, so they can't be
  immutable.  Backpatch to 9.4 where they were introduced.  Catalog
  version bumped.
  http://git.postgresql.org/pg/commitdiff/0f43a55331c5697caa2054189ad8d1e717ccb192

Tom Lane pushed:

- Allow join removal in some cases involving a left join to a
  subquery.  We can remove a left join to a relation if the relation's
  output is provably distinct for the columns involved in the join
  clause (considering only equijoin clauses) and the relation supplies
  no variables needed above the join.  Previously, the join removal
  logic could only prove distinctness by reference to unique indexes
  of a table.  This patch extends the logic to consider subquery
  relations, wherein distinctness might be proven by reference to
  GROUP BY, DISTINCT, etc.  We actually already had some code to check
  that a subquery's output was provably distinct, but it was hidden
  inside pathnode.c; which was a pretty bad place for it really, since
  that file is mostly boilerplate Path construction and comparison.
  Move that code to analyzejoins.c, which is arguably a more
  appropriate location, and is certainly the site of the new usage for
  it.  David Rowley, reviewed by Simon Riggs
  http://git.postgresql.org/pg/commitdiff/f15821eefd70941d4ec5bd77d75c1da5534ba6b2

- Fix two low-probability memory leaks in regular expression parsing.
  If pg_regcomp failed after having invoked markst/cleanst, it would
  leak any "struct subre" nodes it had created.  (We've already
  detected all regex syntax errors at that point, so the only likely
  causes of later failure would be query cancel or out-of-memory.)  To
  fix, make sure freesrnode knows the difference between the
  pre-cleanst and post-cleanst cleanup procedures.  Add some
  documentation of this less-than-obvious point.  Also, newlacon did
  the wrong thing with an out-of-memory failure from realloc(), so
  that the previously allocated array would be leaked.  Both of these
  are pretty low-probability scenarios, but a bug is a bug, so patch
  all the way back.  Per bug #10976 from Arthur O'Dwyer.
  http://git.postgresql.org/pg/commitdiff/1567e659a877d35ab4b85dafff41b2845d50990f

- Partial fix for dropped columns in functions returning composite.
  When a view has a function-returning-composite in FROM, and there
  are some dropped columns in the underlying composite type,
  ruleutils.c printed junk in the column alias list for the
  reconstructed FROM entry.  Before 9.3, this was prevented by doing
  get_rte_attribute_is_dropped tests while printing the column alias
  list; but that solution is not currently available to us for reasons
  I'll explain below.  Instead, check for empty-string entries in the
  alias list, which can only exist if that column position had been
  dropped at the time the view was made.  (The parser fills in empty
  strings to preserve the invariant that the aliases correspond to
  physical column positions.) While this is sufficient to handle the
  case of columns dropped before the view was made, we have still got
  issues with columns dropped after the view was made.  In particular,
  the view could contain Vars that explicitly reference such columns!
  The dependency machinery really ought to refuse the column drop
  attempt in such cases, as it would do when trying to drop a table
  column that's explicitly referenced in views.  However, we currently
  neglect to store dependencies on columns of composite types, and
  fixing that is likely to be too big to be back-patchable (not to
  mention that existing views in existing databases would not have the
  needed pg_depend entries anyway).  So I'll leave that for a separate
  patch.  Pre-9.3, ruleutils would print such Vars normally (with
  their original column names) even though it suppressed their entries
  in the RTE's column alias list.  This is certainly bogus, since the
  printed view definition would fail to reload, but at least it didn't
  crash.  However, as of 9.3 the printed column alias list is tightly
  tied to the names printed for Vars; so we can't treat columns as
  dropped for one purpose and not dropped for the other.  This is why
  we can't just put back the get_rte_attribute_is_dropped test: it
  results in an assertion failure if the view in fact contains any
  Vars referencing the dropped column.  Once we've got dependencies
  preventing such cases, we'll probably want to do it that way instead
  of relying on the empty-string test used here.  This fix turned up a
  very ancient bug in outfuncs/readfuncs, namely that T_String nodes
  containing empty strings were not dumped/reloaded correctly: the
  node was printed as "<>" which is read as a string value of <>.
  Since (per SQL) we disallow empty-string identifiers, such nodes
  don't occur normally, which is why we'd not noticed.  (Such nodes
  aren't used for literal constants, just identifiers.) Per report
  from Marc Schablewski.  Back-patch to 9.3 which is where the rule
  printing behavior changed.  The dangling-variable case is broken all
  the way back, but that's not what his complaint is about.
  http://git.postgresql.org/pg/commitdiff/9b35ddce93a2ef336498baa15581b9d10f01db9c

- Update time zone data files to tzdata release 2014e.  DST law
  changes in Crimea, Egypt, Morocco.  New zone Antarctica/Troll for
  Norwegian base in Queen Maud Land.
  http://git.postgresql.org/pg/commitdiff/b1864fabf93f23e4eaa5ec4599a143ac8f7647e5

- Fix xreflabel for hot_standby_feedback.  Rather remarkable that this
  has been wrong since 9.1 and nobody noticed.
  http://git.postgresql.org/pg/commitdiff/4cbe3abb3162d14a86bc8ec73fd9331638ec18a0

- First-draft release notes for 9.3.5.  As usual, the release notes
  for older branches will be made by cutting these down, but put them
  up for community review first.  Note: a few of these items actually
  don't apply to 9.3, but only to older branches.  I'll sort that out
  when copying the text into the older release-X.Y.sgml files.
  http://git.postgresql.org/pg/commitdiff/ddc41fd2f4756b529814ad03fa32e8ba10253996

Heikki Linnakangas pushed:

- Fix bugs in SP-GiST search with range type's -|- (adjacent)
  operator.  The consistent function contained several bugs: * The "if
  (which2) { ... }"  block was broken. It compared the * argument's
  lower bound against centroid's upper bound, while it was supposed to
  compare the argument's upper bound against the centroid's lower
  bound (the comment was correct, code was wrong). Also, it cleared
  bits in the "which1" variable, while it was supposed to clear bits
  in "which2".  * If the argument's upper bound was equal to the
  centroid's lower * bound, we descended to both halves (= all
  quadrants). That's unnecessary, searching the right quadrants is
  sufficient. This didn't lead to incorrect query results, but was
  clearly wrong, and slowed down queries unnecessarily.  * In the case
  that argument's lower bound is adjacent to the * centroid's upper
  bound, we also don't need to visit all quadrants. Per similar
  reasoning as previous point.  * The code where we compare the
  previous centroid with the current * centroid should match the code
  where we compare the current centroid with the argument. The point
  of that code is to redo the calculation done in the previous level,
  to see if we were supposed to traverse left or right (or up or
  down), and if we actually did. If we moved in the different
  direction, then we know there are no matches for bound.  Refactor
  the code and adds comments to make it more readable and easier to
  reason about.  Backpatch to 9.3 where SP-GiST support for range
  types was introduced.
  http://git.postgresql.org/pg/commitdiff/1264ef31a399927f9fe02212e10980bf4ba7b9f2

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Christoph Moench-Tegeder sent in a patch to correct an example in
logical decoding.

Steve Singer sent in a patch to fix a bug in walsender keepalives.

Etsuro Fujita sent in a patch to remove some redundant words from a
comment in src/backend/commands/explain.c.

Fabrízio de Royes Mello sent in four more revisions of a patch to
implement ALTER TABLE ... SET LOGGED.

Shigeru HANADA and Kaigai Kouhei traded patches to implement the
custom plan API.

Amit Kapila sent in a patch to fix an issue with pg_basebackup on
Windows with symlinks.

Fujii Masao sent in a patch to fix an issue with pg_receivexlog
--status-interval.  It checked for positive numbers, but should have
checked for nonzero ones.

Dilip Kumar sent in a patch to ensure that \pset correctly shows both
arguments are optional, not just the second.

David Rowley sent in another revision of a patch to allow NOT IN to
use ANTI JOINs in certain cases.

Rajeev Rastogi sent in a patch to fix an issue where there was an
unwanted LOG during recovery of DROP TABLESPACE.

Jeff Janes sent in another revision of a patch to fix issues that
manifested as "Could not open file "pg_multixact/members/xxxx".

Dilip Kumar sent in two more revisions of a patch to enable vacuumdb
to use >1 core in parallel.

Kyotaro HORIGUCHI sent in another revision of a patch to enable using
a UNIQUE index for longer pathkeys.

Kyotaro HORIGUCHI sent in a patch to fix an issue where xmin and xmax
for FDWs give strange results.

Kyotaro HORIGUCHI sent in a patch to change a couple of instances of
BUFFER_LOCK_EXCLUSIVE in src/backend/access/gin/gininsert.c to
GIN_EXCLUSIVE.

Viswanatham Kirankumar sent in a patch to process pg_hba.conf keywords
as case-insensitive.

Fabien COELHO sent in two more revisions of a patch to allow using a
Gaussian distribution in pgbench.

Amit Kapila sent in a patch to fix the fact that pg_basebackup -T
doesn't work on Windows.

Michael Paquier sent in two more revisions of a patch to do better at
HINTing an appropriate column within errorMissingColumn().

Dmitry Voronin sent in another revision of a patch to augment
the sslinfo contrib extension.

Petr (PJMODOS) Jelinek sent in another revision of a patch to allow
setting a new system identifier via pg_resetxlog.

Michael Paquier sent in another revision of a patch to fix some WAL
replay bugs.

MauMau sent in a patch to suppress "autovacuum: found orphan temp
table" messages.

Tomas Vondra sent in another revision of a patch to tweak
NTUP_PER_BUCKET.

Tomas Vondra sent in another revision of a patch to fix an issue where
bad estimation together with large work_mem generates terrible slow
hash joins.

Fabien COELHO sent in two revisions of a patch to fix an issue where
pg_stat_statements is cluttered with "DEALLOCATE dbdpg_p*".

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

David Fetter | 14 Jul 06:19 2014

== PostgreSQL Weekly News - July 13 2014 ==

== PostgreSQL Weekly News - July 13 2014 ==

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.  Send talk proposals to ecpug AT postgresql DOT org.

== PostgreSQL Product News ==

Slony-I 2.2.3, a trigger-based replication system for PostgreSQL, released.
http://www.slony.info/

== PostgreSQL Jobs for July ==

http://archives.postgresql.org/pgsql-jobs/2014-07/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-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.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Bruce Momjian pushed:

- pg_upgrade: allow upgrades for new-only TOAST tables.  Previously,
  when calculations on the need for toast tables changed, pg_upgrade
  could not handle cases where the new cluster needed a TOAST table
  and the old cluster did not.  (It already handled the opposite
  case.)  This fixes the "OID mismatch" error typically generated in
  this case.  Backpatch through 9.2
  http://git.postgresql.org/pg/commitdiff/3088cc37044a303fc50857d8d9e7e44b5c250642

- Adjust blank lines around PG_MODULE_MAGIC defines, for consistency.
  Report by Robert Haas
  http://git.postgresql.org/pg/commitdiff/6a605cd6bd9f689b35676623add0de9b90978bf1

Tom Lane pushed:

- In pg_dump, show server and pg_dump versions with or without
  --verbose.  We used to print this information only in verbose mode,
  but it's argued that it's useful enough to print always; one reason
  being that this provides some documentation about which Postgres
  versions the dump is meant to reload into.  Jing Wang, reviewed by
  Jeevan Chalke
  http://git.postgresql.org/pg/commitdiff/7700597b34fbb26e377f419271f65be1c13c518f

- Don't assume a subquery's output is unique if there's a SRF in its
  tlist.  While the x output of "select x from t group by x" can be
  presumed unique, this does not hold for "select x,
  generate_series(1,10) from t group by x", because we may expand the
  set-returning function after the grouping step.  (Perhaps that
  should be re-thought; but considering all the other oddities
  involved with SRFs in targetlists, it seems unlikely we'll change
  it.) Put a check in query_is_distinct_for() so it's not fooled by
  such cases.  Back-patch to all supported branches.  David Rowley
  http://git.postgresql.org/pg/commitdiff/9e2f2d7a0539460dc76dbf76dfae17024d5e031e

- Implement IMPORT FOREIGN SCHEMA.  This command provides an automated
  way to create foreign table definitions that match remote tables,
  thereby reducing tedium and chances for error.  In this patch, we
  provide the necessary core-server infrastructure and implement the
  feature fully in the postgres_fdw foreign-data wrapper.  Other
  wrappers will throw a "feature not supported" error until/unless
  they are updated.  Ronan Dunklau and Michael Paquier, additional
  work by me
  http://git.postgresql.org/pg/commitdiff/59efda3e50ca4de6a9d5aa4491464e22b6329b1e

- Fix bug with whole-row references to append subplans.
  ExecEvalWholeRowVar incorrectly supposed that it could "bless" the
  source TupleTableSlot just once per query.  But if the input is
  coming from an Append (or, perhaps, other cases?) more than one slot
  might be returned over the query run.  This led to "record type has
  not been registered" errors when a composite datum was extracted
  from a non-blessed slot.  This bug has been there a long time; I
  guess it escaped notice because when dealing with subqueries the
  planner tends to expand whole-row Vars into RowExprs, which don't
  have the same problem.  It is possible to trigger the problem in all
  active branches, though, as illustrated by the added regression
  test.
  http://git.postgresql.org/pg/commitdiff/d68581483564ec0fbfdc255e493c4f5bd165e55e

Fujii Masao pushed:

- Fix typo in comment.  This typo was accidentally added by recent
  commit 4cbd128.
  http://git.postgresql.org/pg/commitdiff/6048896e4c9679cba89242d77f02ceba01c791d1

- Fix typos in comments.
  http://git.postgresql.org/pg/commitdiff/4cbd12832839830fe58bb5d9d4ba7e2ec84952ce

- Add new ECHO mode 'errors' that displays only failed commands in
  psql.  When the psql variable ECHO is set to 'erros', only failed
  SQL commands are printed to standard error output. Also this patch
  adds -b option into psql.  This is equivalent to setting the
  variable ECHO to 'errors'.  Pavel Stehule, reviewed by Fabrízio de
  Royes Mello, Samrat Revagade, Kumar Rajeev Rastogi, Abhijit
  Menon-Sen, and me.
  http://git.postgresql.org/pg/commitdiff/5b214c5dd1de37764797b3fb9164af3c885a7b86

Peter Eisentraut pushed:

- doc: Fix spacing in verbatim environments
  http://git.postgresql.org/pg/commitdiff/53166fe248c1b4b211094e80e54e5ab330dbf957

- doc: Link text to table by id
  http://git.postgresql.org/pg/commitdiff/889313c76b2d0f3388e3008fb309bb71d4c9978b

- Update key words table for 9.4
  http://git.postgresql.org/pg/commitdiff/56abcf6b829adcbadcc73e4eb06caefb50d110bd

- Fix whitespace
  http://git.postgresql.org/pg/commitdiff/8522f21400570fdf6af38c32a2522a5465dccfd5

- Fix whitespace
  http://git.postgresql.org/pg/commitdiff/80ddd04b4d66ad6564b6d77ffc2bd8fb5e0dcdfa

Robert Haas pushed:

- Improve error messages for bytea decoding failures.  Craig Ringer
  http://git.postgresql.org/pg/commitdiff/f73474382cb304b4f043e5de89c28b0365c04156

- Fix error hint style.  Mistake caught by Tom Lane.
  http://git.postgresql.org/pg/commitdiff/b043985b7aaf62f6978a0c567c8340ad9cf1ad67

Magnus Hagander pushed:

- Add autocompletion of locale keywords for CREATE DATABASE.  Adds
  support for autocomplete of LC_COLLATE and LC_CTYPE to the CREATE
  DATABASE command in psql.
  http://git.postgresql.org/pg/commitdiff/deee42ab015d54baa1b9e0165bf3635dab4f9f7a

- Support --with-extra-version equivalent functionality in MSVC build.
  Adds a configuration parameter, extraver, that is appended to the
  version number when built.  Michael Paquier, reviewed by Muhammad
  Asif Naeem
  http://git.postgresql.org/pg/commitdiff/8d9a0e85bd6ab4fe5268a1d759a787f72ff9333e

Andres Freund pushed:

- Fix decoding of consecutive MULTI_INSERTs emitted by one
  heap_multi_insert().  Commit 1b86c81d2d fixed the decoding of
  toasted columns for the rows contained in one xl_heap_multi_insert
  record. But that's not actually enough, because heap_multi_insert()
  will actually first toast all passed in rows and then emit several
  *_multi_insert records; one for each page it fills with tuples.  Add
  a XLOG_HEAP_LAST_MULTI_INSERT flag which is set in
  xl_heap_multi_insert->flag denoting that this multi_insert record is
  the last emitted by one heap_multi_insert() call. Then use that flag
  in decode.c to only set clear_toast_afterwards in the right
  situation.  Expand the number of rows inserted via COPY in the
  corresponding regression test to make sure that more than one heap
  page is filled with tuples by one heap_multi_insert() call.
  Backpatch to 9.4 like the previous commit.
  http://git.postgresql.org/pg/commitdiff/626bfad6cc5701eb385b8995e1431ad6a5f24928

- Minimal psql tab completion support for SET search_path.  Complete
  SET search_path = ... to non-temporary and non-toast schemas. Since
  there pretty much is no use case to add those to the search path and
  there can be many it's helpful to exclude them.  It'd be nicer to
  complete multiple search path elements, but that's not easy.  Jeff
  Janes
  http://git.postgresql.org/pg/commitdiff/bd409519bd19911d2d2cba64415447d2fa9d766b

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Abhijit Menon-Sen sent in another revision of a patch to introduce
XLogLockBlockRangeForCleanup().

Abhijit Menon-Sen sent in another revision of a patch to add a
--stats option to xlogdump.

Kaigai Kouhei sent in another revision of a patch to implement a
custom plan API.

Etsuro Fujita sent in a WIP patch to optimize updating foreign tables
in the PostgreSQL FDW.

David Rowley sent in two more revisions of a patch to allow removing
LEFT JOINs under certain circumstances.

Haribabu Kommi sent in another revision of a patch to add min() and
max() for the inet data type.

Amit Kapila sent in another revision of a patch to fix an issue with
duplicate parameters in ALTER SYSTEM.

Dilip Kumar sent in another revision of a patch to allow parallel
cores to be used by vacuumdb.

SAWADA Masahiko and Jeevan Chalke traded patches to add line number as
prompt option to psql.

Alvaro Herrera sent in another revision of a patch to add minmax
indexes.

Tomonari Katsumata sent in a patch to ensure that rounding up time
value is not less than its unit.

Furuya Osamu sent in another revision of a patch to add a synchronous
mode to pg_receivexlog.

SAWADA Masahiko sent in a patch to fix an issue in timeout of
pg_receivexlog --status-interval.

Alvaro Herrera sent in a patch to fix the README in anticipation of
another patch for CSN-based snapshots.

Kyotaro HORIGUCHI and Michael Paquier traded patches to fix an issue
in WAL replay.

Jeff Davis sent in another revision of a patch to allow IGNORE NULLS
in the lead() and lag() windowing functions.

Jeff Davis sent in two revisions of a patch to Allow multi-byte
characters as escape in SIMILAR TO and SUBSTRING.

Tom Lane sent in another revision of a patch to allow NOT IN to use
ANTI joins.

Tomas Vondra sent in two more revisions of a patch to tweak
NTUP_PER_BUCKET.

Ali Akbar sent in another revision of a patch to fix xpath() to return
namespace definitions.

Etsuro Fujita sent in a patch to fix an incorrect comment in
postgres_fdw.c.

Christoph Martin sent in a patch to fix the search_path default value
separator.

Etsuro Fujita sent in a patch to add information on exact/lossy blocks
for a bitmap heap scan when both the numbers of exact/lossy pages
retrieved by the node are zero.

Noah Misch sent in a patch to fix an OpenLDAP issue.

Fabrízio de Royes Mello sent in another revision of a patch to add
ALTER TABLE ... SET LOGGED.

Christoph Berg sent in another revision of a patch to secure "make
check."

Magnus Hagander sent in a patch to include SSL compression info in a
psql header.

Emre Hesegeli sent in a patch to add selectivity estimation for inet
operators.

Tomas Vondra sent in another revision of a patch to fix an issue where
bad estimation together with large work_mem generates slow hash joins.

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Jaime Casanova | 13 Jul 09:48 2014

PgDay Ecuador 2014: Call for papers

Hi,

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.

We are now accepting proposals for talks. Each session will last 45
minutes and can be about any topic related to PostgreSQL. Possible
topics include:

- Developing applications for PostgreSQL
- Administering large scale PostgreSQL installations
- Case studies and/or success stories of PostgreSQL deployments
- PostgreSQL tools and utilities
- PostgreSQL hacking
- Tuning the server
- Migrating from other systems
- Scaling/replication
- Benchmarking & hardware
- PostgreSQL related products

Of course, we will be happy to receive proposals for talks on other
PostgreSQL-related topics.

Also I would like to propose a section of lightning talks (or maybe a
forum or "questions and answers" section) about features that users
would like to see in PostgreSQL or current limitations that have
prevented them from implementing their projects in PostgreSQL.

Proposals should be sent to ecpug <at> postgresql.org or to
jaime <at> 2ndquadrant.com until August 31st, 2014 (requests sent to any
other email will be ignored.) If your talk is selected you will be
notified by September 21st.

We look forward to hearing from you, and see you in Quito in PgDay Ecuador 2014!

-- 
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566         Cell: +593 987171157

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

David Fetter | 7 Jul 06:44 2014

== PostgreSQL Weekly News - July 06 2014 ==

== PostgreSQL Weekly News - July 06 2014 ==

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-en/

== PostgreSQL Product News ==

Database Designer for PostgreSQL 1.10.0, a CASE tool which works
natively under the Windows OS family, released.
http://microolap.com/products/database/postgresql-designer/download/

== PostgreSQL Jobs for July ==

http://archives.postgresql.org/pgsql-jobs/2014-07/threads.php

== PostgreSQL Local ==

Char(14) and PGday UK will be held July 8 and 9, 2014.
http://www.char14.info
http://postgresqlusergroup.org.uk/

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PostgreSQL Conference Europe 2014 will be held on October 21-24 in
Madrid, Spain, at the Hotel Miguel Angel. 
http://2014.pgconf.eu/

== 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.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Heikki Linnakangas pushed:

- Fix and enhance the assertion of no palloc's in a critical section.
  The assertion failed if WAL_DEBUG or LWLOCK_STATS was enabled; fix
  that by using separate memory contexts for the allocations made
  within those code blocks.  This patch introduces a mechanism for
  marking any memory context as allowed in a critical section.
  Previously ErrorContext was exempt as a special case.  Instead of a
  blanket exception of the checkpointer process, only exempt the
  memory context used for the pending ops hash table.
  http://git.postgresql.org/pg/commitdiff/1c6821be31f91ab92547a8ed4246762c8cefb1b3

Andres Freund pushed:

- Fix typos in the cluster_name commit.  Thom Brown and Fujii Masao
  http://git.postgresql.org/pg/commitdiff/6647f59fd256927aaf9e35929b5c284d10d18839

- Check interrupts during logical decoding more frequently.  When
  reading large amounts of preexisting WAL during logical decoding
  using the SQL interface we possibly could fail to check interrupts
  in due time. Similarly the same could happen on systems with a very
  high WAL volume while creating a new logical replication slot,
  independent of the used interface.  Previously these checks where
  only performed in xlogreader's read_page callbacks, while waiting
  for new WAL to be produced. That's not sufficient though, if there's
  never a need to wait.  Walsender's send loop already contains a
  interrupt check.  Backpatch to 9.4 where the logical decoding
  feature was introduced.
  http://git.postgresql.org/pg/commitdiff/1cbc9480106241aaa8db112331e93d0a265b6db0

- Rename logical decoding's pg_llog directory to pg_logical.  The old
  name wasn't very descriptive as of actual contents of the directory,
  which are historical snapshots in the snapshots/ subdirectory and
  mappingdata for rewritten tuples in mappings/. There's been a fair
  amount of discussion what would be a good name. I'm settling for
  pg_logical because it's likely that further data around logical
  decoding and replication will need saving in the future.  Also add
  the missing entry for the directory into storage.sgml's list of
  PGDATA contents.  Bumps catversion as the data directories won't be
  compatible.
  http://git.postgresql.org/pg/commitdiff/a36a8fa376631e59d006772bcd30f4f827d7e6b9

- Fix decoding of MULTI_INSERTs when rows other than the last are
  toasted.  When decoding the results of a HEAP2_MULTI_INSERT
  (currently only generated by COPY FROM) toast columns for all but
  the last tuple weren't replaced by their actual contents before
  being handed to the output plugin. The reassembled toast datums
  where disregarded after every
  REORDER_BUFFER_CHANGE_(INSERT|UPDATE|DELETE) which is correct for
  plain inserts, updates, deletes, but not multi inserts - there we
  generate several REORDER_BUFFER_CHANGE_INSERTs for a single
  xl_heap_multi_insert record.  To solve the problem add a
  clear_toast_afterwards boolean to ReorderBufferChange's union member
  that's used by modifications. All row changes but multi_inserts
  always set that to true, but multi_insert sets it only for the last
  change generated.  Add a regression test covering decoding of
  multi_inserts - there was none at all before.  Backpatch to 9.4
  where logical decoding was introduced.  Bug found by Petr Jelinek.
  http://git.postgresql.org/pg/commitdiff/1b86c81d2d255d3fb665ddc77c2bc3dfd751a1df

Noah Misch pushed:

- Don't prematurely free the BufferAccessStrategy in pgstat_heap().
  This function continued to use it after heap_endscan() freed it.  In
  passing, don't explicit create a strategy here.  Instead, use the
  one created by heap_beginscan_strat(), if any.  Back-patch to 9.2,
  where use of a BufferAccessStrategy here was introduced.
  http://git.postgresql.org/pg/commitdiff/9d0826c595e2a376f6645eb575a9d81d5f5ececf

- Consistently pass an "unsigned char" to ctype.h functions.  The
  isxdigit() calls relied on undefined behavior.  The isascii() call
  was well-defined, but our prevailing style is to include the cast.
  Back-patch to 9.4, where the isxdigit() calls were introduced.
  http://git.postgresql.org/pg/commitdiff/333b7db8b39679acf0665b3fc4ad99cbc14fbba7

Bruce Momjian pushed:

- pg_upgrade:  update C comments about pg_dumpall.  There were some C
  comments that hadn't been updated from the switch of using only
  pg_dumpall to using pg_dump and pg_dumpall, so update them.  Also,
  don't bother using --schema-only for pg_dumpall --globals-only.
  Backpatch through 9.4
  http://git.postgresql.org/pg/commitdiff/55863274d98556acf57013f64f545d9a1e640bba

- pg_upgrade:  no need to remove "members" files for pre-9.3 upgrades.
  Per analysis by Alvaro Herrera.  Backpatch through 9.3
  http://git.postgresql.org/pg/commitdiff/89cf2d5203085a3b74ab8ce1f323c93f8e410473

- pg_upgrade:  preserve database and relation minmxid values.  Also
  set these values for pre-9.3 old clusters that don't have values to
  preserve.  Analysis by Alvaro Herrera.  Backpatch through 9.3.
  http://git.postgresql.org/pg/commitdiff/a61daa14d56867e90dc011bbba52ef771cea6770

Tom Lane pushed:

- Allow empty replacement strings in contrib/unaccent.  This is useful
  in languages where diacritic signs are represented as separate
  characters; it's also one step towards letting unaccent be used for
  arbitrary substring substitutions.  In passing, improve the user
  documentation for unaccent, which was sadly vague about some
  important details.  Mohammad Alhashash, reviewed by Abhijit
  Menon-Sen
  http://git.postgresql.org/pg/commitdiff/97c40ce61465582b96944e41ed6ec06c2016b95c

- Allow multi-character source strings in contrib/unaccent.  This
  could be useful in languages where diacritic signs are represented
  as separate characters; more generally it supports using unaccent
  dictionaries for substring substitutions beyond narrowly conceived
  "diacritic removal".  In any case, since the rule-file parser
  doesn't complain about multi-character source strings, it behooves
  us to do something unsurprising with them.
  http://git.postgresql.org/pg/commitdiff/1b2488731cc2c87cc9a4cb8d654e4d9981fdf9ac

- Issue a WARNING about invalid rule file format in contrib/unaccent.
  We were already issuing a WARNING, albeit only elog not ereport, for
  duplicate source strings; so warning rather than just being
  stoically silent seems like the best thing to do here.  Arguably
  both of these complaints should be upgraded to ERRORs, but that
  might be more behavioral change than people want.  Note: the faulty
  line is already printed via an errcontext hook, so there's no need
  for more information than these messages provide.
  http://git.postgresql.org/pg/commitdiff/03a25cec8de3737924c9dd33bb868d4bc7a33ad5

- Fix inadequately-sized output buffer in contrib/unaccent.  The
  output buffer size in unaccent_lexize() was calculated as input
  string length times pg_database_encoding_max_length(), which
  effectively assumes that replacement strings aren't more than one
  character.  While that was all that we previously documented it to
  support, the code actually has always allowed replacement strings of
  arbitrary length; so if you tried to make use of longer strings, you
  were at risk of buffer overrun.  To fix, use an expansible
  StringInfo buffer instead of trying to determine the maximum space
  needed a-priori.  This would be a security issue if unaccent rules
  files could be installed by unprivileged users; but fortunately they
  can't, so in the back branches the problem can be labeled as
  improper configuration by a superuser.  Nonetheless, a memory stomp
  isn't a nice way of reacting to improper configuration, so let's
  back-patch the fix.
  http://git.postgresql.org/pg/commitdiff/5a421a47eb1fc4398f42678c09e35aa72dc7cf18

- Improve handling of OOM score adjustment in sample Linux start
  script.  Per a suggestion from Christoph Berg.
  http://git.postgresql.org/pg/commitdiff/f23425fa950fec3aff458de117037c9caadbc35c

- Remove some useless code in the configure script.  Almost ten years
  ago, commit e48322a6d6cfce1ec52ab303441df329ddbc04d1 broke the logic
  in ACX_PTHREAD by looping through all the possible flags rather than
  stopping with the first one that would work.  This meant that
  $acx_pthread_ok was no longer meaningful after the loop; it would
  usually be "no", whether or not we'd found working thread flags.
  The reason nobody noticed is that Postgres doesn't actually use any
  of the symbols set up by the code after the loop.  Rather than
  complicate things some more to make it work as designed, let's just
  remove all that dead code, and thereby save a few cycles in each
  configure run.
  http://git.postgresql.org/pg/commitdiff/2e8ce9ae46d15b2bfd34c2d53193da9858d3471a

- Refactor CREATE/ALTER DATABASE syntax so options need not be
  keywords.  Most of the existing option names are keywords anyway,
  but we can get rid of LC_COLLATE and LC_CTYPE as keywords known to
  the lexer/grammar.  This immediately reduces the size of the grammar
  tables by about 8KB, and will save more when we add additional
  CREATE/ALTER DATABASE options in future.  A side effect of the
  implementation is that the CONNECTION LIMIT option can now also be
  spelled CONNECTION_LIMIT.  We choose not to document this, however.
  Vik Fearing, based on a suggestion by me; reviewed by Pavel Stehule
  http://git.postgresql.org/pg/commitdiff/15c82efd6994affd1d5654d13bc8911a9faff659

- Allow CREATE/ALTER DATABASE to manipulate datistemplate and
  datallowconn.  Historically these database properties could be
  manipulated only by manually updating pg_database, which is
  error-prone and only possible for superusers.  But there seems no
  good reason not to allow database owners to set them for their
  databases, so invent CREATE/ALTER DATABASE options to do that.
  Adjust a couple of places that were doing it the hard way to use the
  commands instead.  Vik Fearing, reviewed by Pavel Stehule
  http://git.postgresql.org/pg/commitdiff/fbb1d7d73f8e23a3a61e702629c53cef48cb0918

- Add some errdetail to checkRuleResultList().  This function wasn't
  originally thought to be really user-facing, because converting a
  table to a view isn't something we expect people to do manually.  So
  not all that much effort was spent on the error messages; in
  particular, while the code will complain that you got the column
  types wrong it won't say exactly what they are.  But since we
  repurposed the code to also check compatibility of rule RETURNING
  lists, it's definitely user-facing.  It now seems worthwhile to add
  errdetail messages showing exactly what the conflict is when there's
  a mismatch of column names or types.  This is prompted by bug #10836
  from Matthias Raffelsieper, which might have been forestalled if the
  error message had reported the wrong column type as being "record".
  Back-patch to 9.4, but not into older branches where the set of
  translatable error strings is supposed to be stable.
  http://git.postgresql.org/pg/commitdiff/7980ab30ecf36162699f138697e2ff5589d9063e

- Improve support for composite types in PL/Python.  Allow PL/Python
  functions to return arrays of composite types.  Also, fix the
  restriction that plpy.prepare/plpy.execute couldn't handle query
  parameters or result columns of composite types.  In passing, adopt
  a saner arrangement for where to release the tupledesc reference
  counts acquired via lookup_rowtype_tupdesc.  The callers of
  PLyObject_ToCompositeDatum were doing the lookups, but then the
  releases happened somewhere down inside subroutines of
  PLyObject_ToCompositeDatum, which is bizarre and bug-prone.  Instead
  release in the same function that acquires the refcount.  Ed Behn
  and Ronan Dunklau, reviewed by Abhijit Menon-Sen
  http://git.postgresql.org/pg/commitdiff/8b6010b8350a1756cd85595705971df81b5ffc07

- Redesign API presented by nodeAgg.c for ordered-set and similar
  aggregates.  The previous design exposed the input and output
  ExprContexts of the Agg plan node, but work on grouping sets has
  suggested that we'll regret doing that.  Instead provide more
  narrowly-defined APIs that can be implemented in multiple ways,
  namely a way to get a short-term memory context and a way to
  register an aggregate shutdown callback.  Back-patch to 9.4 where
  the bad APIs were introduced, since we don't want third-party code
  using these APIs and then having to change in 9.5.  Andrew Gierth
  http://git.postgresql.org/pg/commitdiff/6f5034eda05c4946b65858fb8831d069f2873083

- Don't cache per-group context across the whole query in
  orderedsetaggs.c.  Although nodeAgg.c currently uses the same
  per-group memory context for all groups of a query, that might
  change in future.  Avoid assuming it.  This costs us an extra
  AggCheckCallContext() call per group, but that's pretty cheap and is
  probably good from a safety standpoint anyway.  Back-patch to 9.4 in
  case any third-party code copies this logic.  Andrew Gierth
  http://git.postgresql.org/pg/commitdiff/ecd657974478fc713fdc3a625d648cd6a985e3e6

Robert Haas pushed:

- Avoid copying index tuples when building an index.  The previous
  code, perhaps out of concern for avoid memory leaks, formed the
  tuple in one memory context and then copied it to another memory
  context.  However, this doesn't appear to be necessary, since
  index_form_tuple and the functions it calls take precautions against
  leaking memory.  In my testing, building the tuple directly inside
  the sort context shaves several percent off the index build time.
  Rearrange things so we do that.  Patch by me.  Review by Amit
  Kapila, Tom Lane, Andres Freund.
  http://git.postgresql.org/pg/commitdiff/9f03ca915196dfc871804a1f8aad26207f601fd6

- Remove swpb-based spinlock implementation for ARMv5 and earlier.
  Per recent analysis by Andres Freund, this implementation is in fact
  unsafe, because ARMv5 has weak memory ordering, which means tha the
  CPU could move loads or stores across the volatile store performed
  by the default S_UNLOCK.  We could try to fix this, but have no
  ARMv5 hardware to test on, so removing support seems better.  We can
  still support ARMv5 systems on GCC versions new enough to have
  built-in atomics support for this platform, and can also re-add
  support for the old way if someone has hardware that can be used to
  test a fix.  However, since the requirement to use a relatively-new
  GCC hasn't been an issue for ARMv6 or ARMv7, which lack the swpb
  instruction altogether, perhaps it won't be an issue for ARMv5
  either.
  http://git.postgresql.org/pg/commitdiff/4893ccd02459fdb444f4f4b34c441eb899592879

Fujii Masao pushed:

- Prevent psql from issuing BEGIN before ALTER SYSTEM when AUTOCOMMIT
  is off.  The autocommit-off mode works by issuing an implicit BEGIN
  just before any command that is not already in a transaction block
  and is not itself a BEGIN or other transaction-control command, nor
  a command that cannot be executed inside a transaction block. This
  commit prevents psql from issuing such an implicit BEGIN before
  ALTER SYSTEM because it's not allowed inside a transaction block.
  Backpatch to 9.4 where ALTER SYSTEM was added.  Report by Feike
  Steenbergen
  http://git.postgresql.org/pg/commitdiff/d97e98e8337e915e3404f7b2a8a6b966b6f5394f

- Split out the description of page-level lock as new subsection in
  document.  Michael Banck
  http://git.postgresql.org/pg/commitdiff/644d85351e6aa364d31d6c5402e4fd6a3e94e91d

- Refactor pg_receivexlog main loop code, for readability.  Previously
  the source codes for receiving the data and for polling the socket
  were included in pg_receivexlog main loop.  This commit splits out
  them as separate functions. This is useful for improving the
  readability of main loop code and making the future
  pg_receivexlog-related patch simpler.
  http://git.postgresql.org/pg/commitdiff/74cbe966fe2d76de1d607d933c98c144dab58769

- Fix double-free bug of WAL streaming buffer in pg_receivexlog.  This
  bug was introduced while refactoring in commit 74cbe96.
  http://git.postgresql.org/pg/commitdiff/4ccac92d08f22ef0f8df29ea6bd9d5e77bf1d246

Kevin Grittner pushed:

- Smooth reporting of commit/rollback statistics.  If a connection
  committed or rolled back any transactions within a
  PGSTAT_STAT_INTERVAL pacing interval without accessing any tables,
  the reporting of those statistics would be held up until the
  connection closed or until it ended a PGSTAT_STAT_INTERVAL interval
  in which it had accessed a table.  This could result in under-
  reporting of transactions for an extended period, followed by a
  spike in reported transactions.  While this is arguably a bug, the
  impact is minimal, primarily affecting, and being affected by,
  monitoring software.  It might cause more confusion than benefit to
  change the existing behavior in released stable branches, so apply
  only to master and the 9.4 beta.  Gurjeet Singh, with review and
  editing by Kevin Grittner, incorporating suggested changes from
  Abhijit Menon-Sen and Tom Lane.
  http://git.postgresql.org/pg/commitdiff/ac46de56eab9bb93c23c7f34070f3a16e7e76743

- Remove dead typeStruct variable from plpy_spi.c.  Left behind by
  8b6010b8350a1756cd85595705971df81b5ffc07.
  http://git.postgresql.org/pg/commitdiff/e254ff21d1286fe5c2b5ecdfa9bb6b15a7830fcd

Peter Eisentraut pushed:

- Use a separate temporary directory for the Unix-domain socket.
  Creating the Unix-domain socket in the build directory can run into
  name-length limitations.  Therefore, create the socket file in the
  default temporary directory of the operating system.  Keep the
  temporary data directory etc. in the build tree.
  http://git.postgresql.org/pg/commitdiff/f545d233ebce6971b6f9847680e48b679e707d22

- Support vpath builds in TAP tests
  http://git.postgresql.org/pg/commitdiff/0490db62871dc6888c52bd9465d9ade16ab8e795

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Noah Misch, Kyotaro HORIGUCHI and Etsuro Fujita traded patches around
allowing foreign tables to be part of table inheritance hierarchies.

Andres Freund sent in another revision of a patch to add a
cluster_name GUC, which controls whether same is visible in ps output.

Abhijit Menon-Sen and Marti Raudsepp traded patches to add a --stats
option to pg_xlogdump.

Pavel Stehule sent in two more revisions of a patch to allow psql to
show only failed queries.

Michael Paquier sent in another revision of a patch to extend MSVC
scripts to support --with-extra-version.

Heikki Linnakangas sent in another revision of a patch to change the
WAL format and API.

Michael Paquier and Ronan Dunklau traded patches for IMPORT FOREIGN
SCHEMA.

Tomas Vondra sent in three more revisions of a patch to make hash
buckets grow appropriately.

Kyotaro HORIGUCHI sent in a patch to break socket-blocking on
termination.

Kevin Grittner sent in another revision of a patch to add a C
extension to test delta relations in AFTER triggers.

Robert Haas and Andres Freund traded patches to simulate memory
barriers on platforms where they are not available.

Gurjeet Singh sent in another revision of a patch to send transaction
commit/rollback stats to the stats collector unconditionally.

Kyotaro HORIGUCHI sent in a patch to correct the documentation of
ALTER USER SET local_preload_libraries.

Ronan Dunklau sent in another revision of a patch to improve the
functionality of arrays of composite types returned from PL/Python.

Dilip Kumar sent in three more revisions of a patch to allow vacuumdb
to use multiple cores in parallel.

Michael Paquier sent two flocks of patches to fix an issue in WAL
replay.

Fujii Masao sent in another revision of a patch to make
log_disconnections PGC_SUSET rather than PGC_SIGHUP.

Michael Banck sent in a patch to add an additional documentation
subsection for page-level locks in the explicit-locking section.

Ian Lawrence Barwick sent in another revision of a patch to add
a "RETURNING PRIMARY KEY" syntax extension to DML.

Fabien COELHO sent in two more revisions of a patch to add a Gaussian
distribution to pgbench.

Peter Geoghegan sent in another revision of a patch to do  better at
HINTing an appropriate column within errorMissingColumn().

Tomas Vondra sent in another revision of a patch to tweak
NTUP_PER_BUCKET.

Tatsuo Ishii sent in another revision of a patch to add a
shared_memory_type GUC.

Abhijit Menon-Sen sent in two more revisions of a patch to introduce
XLogLockBlockRangeForCleanup().

Rahila Syed sent in two more revisions of a patch to allow various
compression algorithms for full page writes.

Andrew (RhodiumToad) Gierth sent in two patch sets intended to be
infrastructure for GROUPING SETS.

Furuya Osamu sent in another revision of a patch add a synchronous
mode to pg_receivexlog.

Thomas Munro sent in a PoC patch to enable DISTINCT with btree skip
scan (a.k.a. "loose index scan").

David Rowley sent in another revision of a patch to allow NOT IN to
use ANTI joins.

David Rowley sent in another revision of a patch to allow subquery
LEFT JOIN removal where that would produce correct results.

Andrew (RhodiumToad) Gierth sent in two revisions of a patch to fix a
performance regression related to ScalarArrayOpExpr.

Craig Ringer sent in a patch to improve bytea error messages.

Emre Hasegeli sent in another revision of a patch to add selectivity
estimation for inet operators.

SAWADA Masahiko sent in another revision of a patch to add line number
as prompt option to psql.

Jeff Davis sent in another revision of a patch to make it possible for
the LAG and LEAD window functions to ignore nulls.

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Steve Singer | 8 Jul 03:54 2014

Slony 2.2.3 released

The Slony team is pleased to announce Slony 2.2.3 the next minor release 
of the Slony 2.2.x series

Slony 2.2.3 includes the following changes

  - Bug 338 - Have ddlScript return a bigint instead of a integer
  - fixing  Deadlock with application during minor version slony upgrade
  - Bug 342 FAILOVER fixes for some multi-node configurations
  - Remove HAVE_POSIX_SIGNALS from config.h
  - Bug 344 Do not abort reading slon config values when an unrecognized 
one is encountered

Slony 2.2.3 can be downloaded from from the following URL

http://main.slony.info/downloads/2.2/source/slony1-2.2.3.tar.bz2

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Guillaume Lelarge | 7 Jul 22:07 2014

Reminder, only 20 days left: Call for Papers - PostgreSQL Conference Europe 2014

Hi,

PostgreSQL Conference Europe 2014 will be held on October 21-24 in the Hotel Miguel Angel in Madrid, Spain. 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://2014.pgconf.eu/.

We are now accepting proposals for talks, in english or spanish. If you are submitting a talk in Spanish, please write a short summary of the abstract in English in
the "submission notes" field.

Each session will last 45 minutes, and may be on any topic related to PostgreSQL. Suggested topic areas include:

  • Developing applications for PostgreSQL
  • Administering large scale PostgreSQL installations
  • Case studies and/or success stories of PostgreSQL deployments
  • PostgreSQL tools and utilities
  • PostgreSQL hacking
  • Community & user groups
  • Tuning the server
  • Migrating from other systems
  • Scaling/replication
  • Benchmarking & hardware
  • PostgreSQL related products

Of course, we're happy to receive proposals for talks on other PostgreSQL related topics as well.

We may also have a limited number of longer, 90-minute, slots available. Please indicate clearly in your submission if you wish to make a 90-minute talk.

Finally, there will be a session of five minute lightning talks. A separate call for proposals will be made for them further on.

The submission deadline is July 21nd. Selected speakers will be notified before August 18th, 2013.

Please submit your proposals by going to http://2014.pgconf.eu/callforpapers/ and following the instructions there.

The proposals will be considered by committee who will produce a schedule to be published nearer the conference date.

All selected speakers will get free entry to the conference (excluding training sessions). We do not in general cover travel and accommodations for speakers, but may be able to do that in limited cases. If you require assistance with funding to be able to attend, please make a note of this in the submission notes field.

This call for papers is also available on the web at http://2014.pgconf.eu/callforpapers/

We look forward to hearing from you, and seeing you in Madrid in October!


--

Gmane