== PostgreSQL Weekly News - May 25 2014 ==

== PostgreSQL Weekly News - May 25 2014 ==

Congratulations to Andres Freund on his new status as a PostgreSQL
committer.

Commitfests for 9.5 begin on June 15, August 15, October 15, December
15, and February 15.  Beta will be in June 2015.

The first Swiss Postgres Conference will be on June 24th, 2014 at the
HSR Hochschule für Technik Rapperswil.
http://www.postgres-conference.ch/

The second Singapore PostgreSQL Hangount will be 28th May, 2014 at
4:30 PM SGT / 2:00 PM IST / 8:30 AM GMT.  RSVP:
https://plus.google.com/u/0/events/cvpgsaauh8i1l8a7k22jqu5t0jo

== PostgreSQL Product News ==

DBD::Pg version 3.2.1 released (Perl Postgres driver):
http://search.cpan.org/dist/DBD-Pg/

pg_repack 1.2, a utility for removing bloat and restoring the physical
ordering of clustered indexes on line, released.
http://reorg.github.io/pg_repack/

Security updates 2.0.6 and 2.1.13 for PostGIS, the industry standard
geographic information system for PostgreSQL, released.
http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3

tds_fdw 1.0.0, a foreign data wrapper for MS-SQL Server and Sybase,
released.
https://github.com/GeoffMontee/tds_fdw/releases

== PostgreSQL Jobs for May ==

http://archives.postgresql.org/pgsql-jobs/2014-05/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/

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

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.  The
CfP is open!
http://postgresopen.org/2014/callforpapers/

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

== Applied Patches ==

Bruce Momjian pushed:

- doc:  improve 9.4 release notes.  Patch by Andres Freund
  http://git.postgresql.org/pg/commitdiff/4d30d4b9d725211859c63a18e458015636d24b94

- doc:  9.4 release note adjustements.  Text from David G Johnston
  http://git.postgresql.org/pg/commitdiff/b05d1e3c0b2477797cd04b1e8dd1d3b91306e671

- doc:  adjust JSONB 9.4 release note item.  Report by Andrew Dunstan
  http://git.postgresql.org/pg/commitdiff/009ca5e7821d742ed118a87c756c857895f3ffdd

- doc:  9.4 release notes update for pg_bench line limit item.  Report
  by David Johnston
  http://git.postgresql.org/pg/commitdiff/6a61308fba6f474c840192052bca8c86df95927c

- doc:  add ALTER TABLE lock level item as major 9.4 item.  Report by
  Simon Riggs
  http://git.postgresql.org/pg/commitdiff/2e1b5d3f014206f6bdf3dc48d50ecec9dee10fd6

- doc:  link/caps fixes for 9.4 release notes.  Report by Tomonari
  Katsumata
  http://git.postgresql.org/pg/commitdiff/37828e87aec2eb0c15655d4ad753644be851e59f

Tom Lane pushed:

- Fix non-C89-compatible coding in pgbench.  C89 says that compound
  initializers may only contain constant expressions; a restriction
  violated by commit 89d00cbe.  While we've had no actual field
  complaints about this, C89 is still the project standard, and it's
  not saving all that much code to break compatibility here.  So let's
  adhere to the old restriction.  In passing, replace a bunch of
  hardwired constants "256" with sizeof(target-variable), just because
  the latter is more readable and less breakable.  And const-ify where
  possible.  Back-patch to 9.3 where the nonportable code was added.
  Andres Freund and Tom Lane
  http://git.postgresql.org/pg/commitdiff/e41cc470bb57a0f3a765fa44b77ef104b5a5a01e

- Update obsolete comment.  Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/a0841ecd2518d4505b96132b764b918ab5d21ad4

- Prevent auto_explain from changing the output of a user's EXPLAIN.
  Commit af7914c6627bcf0b0ca614e9ce95d3f8056602bf, which introduced
  the EXPLAIN (TIMING) option, for some reason coded explain.c to look
  at planstate->instrument->need_timer rather than es->timing to
  decide whether to print timing info.  However, the former flag might
  get set as a result of contrib/auto_explain wanting timing
  information.  We certainly don't want activation of auto_explain to
  change user-visible statement behavior, so fix that.  Also fix an
  independent bug introduced in the same patch: in the code path for a
  never-executed node with a machine-friendly output format, if timing
  was selected, it would fail to print the Actual Rows and Actual
  Loops items.  Per bug #10404 from Tomonari Katsumata.  Back-patch to
  9.2 where the faulty code was introduced.
  http://git.postgresql.org/pg/commitdiff/e416830a296f440acd67afd8599dde5411021fc4

- Allow total number of transactions in pgbench to exceed INT_MAX.
  Change the total-transactions counters from int32 to int64 to
  accommodate cases where we do more than 2^31 transactions during a
  run.  This patch does not change the INT_MAX limit on explicit "-t"
  parameters, but it does allow the product of the -t and -c
  parameters to exceed INT_MAX, or allow a -T limit that is large
  enough that more than 2^31 transactions can be completed.  While
  pgbench did not actually fail in such cases, it did print an
  incorrect total-transactions count, and some of the derived numbers
  such as TPS would have been wrong as well.  Tomas Vondra
  http://git.postgresql.org/pg/commitdiff/9a65fb350717360c505de9df411024d47e55710b

Fujii Masao pushed:

- Fix incorrect column name in pg_stat_replication document.  Fabrízio
  de Royes Mello
  http://git.postgresql.org/pg/commitdiff/eb56812144bb310f7cb2f63e53d6d58f30df95b5

- Fix typo in JSON function document.
  http://git.postgresql.org/pg/commitdiff/f097d70b7227c1f9aa2ed0af1d6deb05367ef657

- Fix typo in comment.  Erik Rijkers
  http://git.postgresql.org/pg/commitdiff/06db9cce22efeb2a2cffa69491dd576adb77b655

- Fix typos in comments.
  http://git.postgresql.org/pg/commitdiff/19a683f69f4bc630ee04f2938e13e46397eb7a2d

Heikki Linnakangas pushed:

- Fix backup-block numbering in redo of b-tree split.  I got the
  backup block numbers off-by-one in the commit that changed the way
  incomplete-splits are handled. I blame the comments, which said
  "backup block 1" and "backup block 2", even though the backup blocks
  are numbered starting from 0, in the macros and functions used in
  replay.  Fix the comments and the code.  Per Jeff Janes' bug report
  about corruption caused by torn page writes.  The incorrect code is
  new in git master, but backpatch the comment change down to 9.0,
  where the numbering in the redo-side macros  was changed.
  http://git.postgresql.org/pg/commitdiff/c91a9b5a285e20e54cf90f3660ce51ce3a5c2ef4

- Message style fixes to pg_recvlogical.  Lowercase help statements.
  Use an existing message to reduce the number of strings to be
  translated.  Euler Taveira
  http://git.postgresql.org/pg/commitdiff/4e92f780123ca862970816d3fa70d3baf2fcbea4

- Fix typos in comments.
  http://git.postgresql.org/pg/commitdiff/51f41e8c0a0b9ce00734ed4702d16601cc55c280

- Fix misc typos in comments.
  http://git.postgresql.org/pg/commitdiff/57b7e83b0d5e192c01e261b76ff0ed0ccd73c37c

- Fix error when trying to delete page with half-dead left sibling.
  The new page deletion code didn't cope with the case the target
  page's right sibling was marked half-dead. It failed a sanity check
  which checked that the downlinks in the parent page match the lower
  level, because a half-dead page has no downlink. To cope, check for
  that condition, and just give up on the deletion if it happens. The
  vacuum will finish the deletion of the half-dead page when it gets
  there, and on the next vacuum after that the empty can be deleted.
  Reported by Jeff Janes.
  http://git.postgresql.org/pg/commitdiff/8da31837803e95f26642019d859c3309d1c125fa

Peter Eisentraut pushed:

- Fix spurious tab character
  http://git.postgresql.org/pg/commitdiff/e12d7320ca494fd05134847e300feedb2d4a5969

- Small typo and formatting fixes in postgresql.conf.sample
  http://git.postgresql.org/pg/commitdiff/0a5faaa90718b0ce259f43bfae8d629cc040a67c

Robert Haas pushed:

- Remove unnecessary cleanup code.  This is all inside a block guarded
  by op == DSM_OP_ATTACH, so it can never be the case that op ==
  DSM_OP_CREATE.  Reported by Coverity.
  http://git.postgresql.org/pg/commitdiff/11ad3b35c25de6edcaa8a7695cb1d58650c546d3

Andres Freund pushed

- Silence a couple of spurious valgrind warnings in inval.c.  Define
  padding bytes in SharedInvalidationMessage structs to be defined.
  Otherwise the sinvaladt.c ringbuffer, which is accessed by multiple
  processes, will cause spurious valgrind warnings about undefined
  memory being used. That's because valgrind remembers the undefined
  bytes from the last local process's store, not realizing that
  another process has written since, filling the previously
  uninitialized bytes.
  http://git.postgresql.org/pg/commitdiff/0564bbe7a1690f025f4424d5a12cb6af9d428c48

- Don't allocate memory inside an Assert() iff in a critical section.
  HeapTupleHeaderGetCmax() asserts that it is only used if the tuple
  has been updated by the current transaction. That check is correct
  and sensible but requires allocating memory if xmax is a multixact.
  When wal_level is set to logical cmax needs to be included in a wal
  record , generated inside a critical section, which can trigger the
  assertion added in 4a170ee9e.  Reported-By: Steve Singer
  http://git.postgresql.org/pg/commitdiff/9fa93530c878a0e23147a65f7d9a62802b22a995

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Jeff Davis sent in a patch to add some Assert()s to the range types
SP-GiST code.

Teodor Sigaev sent in a patch to fix a memory leak in SP-GiST.

Yuto HAYAMIZU sent in a patch intended to fix a bug where the
postmaster crashes with assertion and LWLOCK_STATS enabled.

Michael Paquier sent in two revisions of a doc patch to add a mention
of logical slots in CREATE_REPLICATION_SLOT for the replication
protocol.

David Rowley sent in another revision of a patch to allow join
removals for more join types.

Shigeru HANADA sent in a patch to fix worker_spi to run as non-dynamic
background worker.

Vik Fearing sent in a patch to add SQL access to database attributes.

Ronan Dunklau sent in another revision of a patch to add IMPORT
FOREIGN SCHEMA.

Anastasia Lubennikova sent in a patch to add index-only scans for GiST.

Michael Paquier and Andres Freund traded patches to fix an issue where
pg_recvlogical is not accepting -I to specify start LSN position.

Matteo Beccati sent in a patch to replace OSSP-UUID for Linux and BSD.

Michael Paquier sent in a patch to fix some typos in Solution.pm, one
of the MSVC scripts.