Dan Langille | 1 Dec 01:54 2015

PGCon 2016: 17-21 May


The dates for PGCon 2016 have been determined.

Join us in Ottawa for the 10th annual PGCon May 17-21 as users and developers from around the world gather for what has become a traditional gathering of the PostgreSQL community.

There will be two days of tutorials on Tuesday and Wednesday.  The best of the best will be available to help you learn great things about PostgreSQL and its tools.

On Wednesday, there will be a Developer Unconference (a User Unconference will follow on Saturday).  The Unconference first appeared at PGCon 2013 and was a instant success.  At PGCon 2016, there will be two days of Unconference, one preceding the conference, and one following the conference.  There will be many people who attend both sessions.

For Thursday and Friday, the submitted talks will be presented as everyone gathers in one location to learn, discuss, and collaborate.

Saturday sees the return of the User Unconference, run similar to the format of previous years. People show up, voice their opinions on what they'd like to hear or would like to speak about, the topics are upon, and the items with the most votes gets onto the schedule. 

In summary:

• Tutorials: 17-18 May 2016 (Tue & Wed)
• Unconference: 18 & 21 May 2016
   • Wednesday is a developer unconference.
   • Saturday is a user unconference.
   • Everyone is welcome to both sessions, but you must register separately for each.
• Talks: 19-20 May 2016 (Thu-Fri).

Registration will open shortly after the talks are announced.

The official Call For Papers announcement will go out on Tuesday.

Dan Langille

Jonathan S. Katz | 30 Nov 16:22 2015

Announcing PGConf US 2016: Apr 18 - 20, NYC - Call for Presentations Open

The call for presentations for PGConf US 2016 is now open! Submissions will be allowed through  January 31st, 2016. All speakers will be notified by February 15, 2016. Please note that as with our past conferences, there will be no extensions of the submission deadline. For more information and submission details, please visit http://www.pgconf.us/2016/submit/

Thanks to the support of our attendees, speakers, volunteers, and sponsors, we have had two incredibly successful PostgreSQL conferences in NYC that have grown the PostgreSQL community substantially. Hundreds of attendees representing a plethora of companies around the world have attended one or both of our previous conferences and continue to join our event. In April of 2016 we plan to keep the tradition going. With the support of the United States PostgreSQL Association, the conference organization team is planning the most informational and involved conference yet.

April 18th is dedicated to hosting trainings and summits. Trainings will occur at the conference venue and the schedule will be announced in February. We are featuring the “Second Annual Regulated Industry Summit: Finance, Government, Healthcare, and PostgreSQL" hosted at the NYC Marriott Brooklyn Bridge, which will bring together PostgreSQL contributors and enterprise developers to discuss challenges and solutions in utilizing PostgreSQL in regulated environments. For more information about the summit and how to attend, please visit http://www.pgconf.us/2016/training/

April 19th - 20th, 2016, will host two days of dedicated sessions, keynotes, and events that will allow individuals to enter and experience the PostgreSQL community at its finest. Experts from around the globe will be submitting talks and trainings in order to grow the PostgreSQL community and empower those involved. This wealth of knowledge comes from the perspectives of developers, DBAs, systems administrators, business-intelligence analysts, decision makers, and the like. 

PGConf US 2016 would not be possible without the considerate support of our sponsors, which allows us to continue to produce a high-quality event while keeping registration fees low to encourage growing our community. We extend a very warm thank you to our launch sponsors:

+ EnterpriseDB
+ OpenSCG
+ Citus Data

+ 2ndQuadrant
+ Amazon Web Services

+ Command Prompt
+ Consistent State

Are you interested in joining these generous businesses in sponsoring the PostgreSQL event of 2016? We invite you to view our sponsorship prospectus slideshow at http://www.pgconf.us/static/prospectus/PGConf-US-2016-Prospectus.pdf

We look forward to seeing everyone in April to make this the best PostgreSQL conference in the United States to date!

For more information, please visit http://www.pgconf.us/
Jakob Egger | 30 Nov 11:39 2015

Announcing Postico, a modern PostgreSQL client for OS X

I'd like to announce Postico, my new PostgreSQL client app for OS X.

Postico has a well-designed graphical user interface targeted at application developers, students and data analysts.


- Postico offers a powerful structure editor for designing tables. Edit column names, types, foreign keys and constraints in an intuitive user interface.

- Browse tables, filter rows, and edit individual rows or even multiple rows at once. Postico is has great data entry tools suitable for business users and developers alike.

- A convenient SQL Query editor for executing complex queries, with support for multiple results

- Postico is also great as a client for data warehousing solutions like Amazon Redshift

After almost a year in Beta, I've now officially released Postico. Postico, which is the successor to PG Commander, is available directly from my website or on the Mac App Store.


Best regards,
Jakob Egger

David Fetter | 30 Nov 05:13 2015

== PostgreSQL Weekly News - November 29 2015 ==

== PostgreSQL Weekly News - November 29 2015 ==

PostgreSQL 9.5 Beta 2 released.

PostgreSQL 9.6devel RPMs are available for testers. Please use only
for crash testing.
http://www.postgresql.org/message-id/1447660638.4285.45.camel <at> gunduz.org

FOSDEM PGDay is a one day conference that will be held ahead of FOSDEM in
Brussels, Belgium, on Jan 29th, 2016.  Details and CfP below:

Prague PostgreSQL Developer Day 2016 (P2D2 2016) is a two-day conference
that will be held on February 17-18 2016 in Prague, Czech Republic.
Czech language web site below:

The first pan-Asian PostgreSQL conference will be held March 2016 in
Singapore.  The CfP is open.

== PostgreSQL Product News ==

barman 1.5.1, a backup and recovery manager for PostgreSQL, released.

== PostgreSQL Jobs for November ==


== PostgreSQL Local ==

PGConf Silicon Valley 2015 is November 17-18 at the South San
Francisco Convention Center.

PGBR2015 (The Brazilian PostgreSQL Conference) will take place in Porto
Alegre, Rio Grande do Sul, on November 18, 19 and 20.  Registration is

Postgres Conference China 2015 will be on November 20-22, 2015 in
http://postgres2015.eventdove.com/   (Chinese)
http://postgrescluster2015.eventdove.com/ (English)

PGConf.DE will be held on November 26-27, 2015 in Hamburg, Germany, at
the Lindner Hotel am Michel.

PostgreSQL <at> SCaLE is a two day, two track event which takes place on Jan.
21-22, 2016, at Pasadena Convention Center, as part of SCaLE 14X.
The CfP is open until Oct 30, 2015.

== 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 ==

Tom Lane pushed:

- Speed up ruleutils' name de-duplication code, and fix
  overlength-name case.  Since commit
  11e131854f8231a21613f834c40fe9d046926387, ruleutils.c has attempted
  to ensure that each RTE in a query or plan tree has a unique alias
  name.  However, the code that was added for this could be quite
  slow, even as bad as O(N^3) if N identical RTE names must be
  replaced, as noted by Jeff Janes.  Improve matters by building a
  transient hash table within set_rtable_names.  The hash table in
  itself reduces the cost of detecting a duplicate from O(N) to O(1),
  and we can save another factor of N by storing the number of
  de-duplicated names already created for each entry, so that we don't
  have to re-try names already created.  This way is probably a bit
  slower overall for small range tables, but almost by definition,
  such cases should not be a performance problem.  In principle the
  same problem applies to the column-name-de-duplication code; but in
  practice that seems to be less of a problem, first because N is
  limited since we don't support extremely wide tables, and second
  because duplicate column names within an RTE are fairly rare, so
  that in practice the cost is more like O(N^2) not O(N^3).  It would
  be very much messier to fix the column-name code, so for now I've
  left that alone.  An independent problem in the same area was that
  the de-duplication code paid no attention to the identifier length
  limit, and would happily produce identifiers that were longer than
  NAMEDATALEN and wouldn't be unique after truncation to NAMEDATALEN.
  This could result in dump/reload failures, or perhaps even views
  that silently behaved differently than before.  We can fix that by
  shortening the base name as needed.  Fix it for both the relation
  and column name cases.  In passing, check for interrupts in
  set_rtable_names, just in case it's still slow enough to be an
  issue.  Back-patch to 9.3 where this code was introduced.

- Fix possible internal overflow in numeric division.  div_var_fast()
  postpones propagating carries in the same way as mul_var(), so it
  has the same corner-case overflow risk we fixed in 246693e5ae8a36f0,
  namely that the size of the carries has to be accounted for when
  setting the threshold for executing a carry propagation step.  We've
  not devised a test case illustrating the brokenness, but the
  required fix seems clear enough.  Like the previous fix, back-patch
  to all active branches.  Dean Rasheed

- Accept flex > 2.5.x in configure.  Per buildfarm member anchovy,
  2.6.0 exists in the wild now.  Hopefully it works with Postgres; if
  not, we'll have to do something about that, but in any case claiming
  it's "too old" is pretty silly.

- Fix thinko: errmsg -> ereport.  Silly mistake in my commit
  09cecdf285ea9f51, reported by Erik Rijkers.  The fact that the
  buildfarm didn't find this implies that we are not testing Perl
  builds that lack MULTIPLICITY, which is a bit disturbing from a
  coverage standpoint.  Until today I'd have said nobody cared about
  such configurations anymore; but maybe not.

- Dodge a macro-name conflict with Perl.  Some versions of Perl export
  a macro named HS_KEY.  This creates a conflict in
  contrib/hstore_plperl against hstore's macro of the same name.  The
  most future-proof solution seems to be to rename our macro; I chose
  HSTORE_KEY.  For consistency, rename HS_VAL and related macros
  similarly.  Back-patch to 9.5.  contrib/hstore_plperl doesn't exist
  before that so there is no need to worry about the conflict in older
  releases.  Per reports from Marco Atzeri and Mike Blackwell.

- Fix handling of inherited check constraints in ALTER COLUMN TYPE
  (again).  The previous way of reconstructing check constraints was
  to do a separate "ALTER TABLE ONLY tab ADD CONSTRAINT" for each
  table in an inheritance hierarchy.  However, that way has no hope of
  reconstructing the check constraints' own inheritance properties
  correctly, as pointed out in bug #13779 from Jan Dirk Zijlstra.
  What we should do instead is to do a regular "ALTER TABLE", allowing
  recursion, at the topmost table that has a particular constraint,
  and then suppress the work queue entries for inherited instances of
  the constraint.  Annoyingly, we'd tried to fix this behavior before,
  in commit 5ed6546cf, but we failed to notice that it wasn't
  reconstructing the pg_constraint field values correctly.  As long as
  I'm touching pg_get_constraintdef_worker anyway, tweak it to always
  schema-qualify the target table name; this seems like useful backup
  to the protections installed by commit 5f173040.  In HEAD/9.5, get
  rid of get_constraint_relation_oids, which is now unused.  (I could
  alternatively have modified it to also return conislocal, but that
  seemed like a pretty single-purpose API, so let's not pretend it has
  some other use.)  It's unused in the back branches as well, but I
  left it in place just in case some third-party code has decided to
  use it.  In HEAD/9.5, also rename pg_get_constraintdef_string to
  pg_get_constraintdef_command, as the previous name did nothing to
  explain what that entry point did differently from others (and its
  comment was equally useless).  Again, that change doesn't seem like
  material for back-patching.  I did a bit of re-pgindenting in
  tablecmds.c in HEAD/9.5, as well.  Otherwise, back-patch to all
  supported branches.

- Adopt the GNU convention for handling tar-archive members exceeding
  8GB.  The POSIX standard for tar headers requires archive member
  sizes to be printed in octal with at most 11 digits, limiting the
  representable file size to 8GB.  However, GNU tar and apparently
  most other modern tars support a convention in which oversized
  values can be stored in base-256, allowing any practical file to be
  a tar member.  Adopt this convention to remove two limitations: *
  pg_dump with -Ft output format failed if the contents of any one
  table exceeded 8GB.  * pg_basebackup failed if the data directory
  contained any file exceeding 8GB.  (This would be a fatal problem
  for installations configured with a table segment size of 8GB or
  more, and it has also been seen to fail when large core dump files
  exist in the data directory.) File sizes under 8GB are still printed
  in octal, so that no compatibility issues are created except in
  cases that would have failed entirely before.  In addition, this
  patch fixes several bugs in the same area: * In 9.3 and later, we'd
  defined tarCreateHeader's file-size argument as size_t, which meant
  that on 32-bit machines it would write a corrupt tar header for file
  sizes between 4GB and 8GB, even though no error was raised.  This
  broke both "pg_dump -Ft" and pg_basebackup for such cases.  *
  pg_restore from a tar archive would fail on tables of size between
  4GB and 8GB, on machines where either "size_t" or "unsigned long" is
  32 bits.  This happened even with an archive file not affected by
  the previous bug.  * pg_basebackup would fail if there were files of
  size between 4GB and 8GB, even on 64-bit machines.  * In 9.3 and
  later, "pg_basebackup -Ft" failed entirely, for any file size, on
  64-bit big-endian machines.  In view of these potential data-loss
  bugs, back-patch to all supported branches, even though removal of
  the documented 8GB limit might otherwise be considered a new feature
  rather than a bug fix.

- Improve div_var_fast(), mostly by making comments better.  The
  integer overflow situation in div_var_fast() is a great deal more
  complicated than the pre-existing comments would suggest.  Moreover,
  the comments were also flat out incorrect as to the precise
  statement of the maxdiv loop invariant.  Upon clarifying that, it
  becomes apparent that the way in which we updated maxdiv after a
  carry propagation pass was overly slow, complex, and conservative:
  we can just reset it to one, which is much easier and also reduces
  the number of times carry propagation occurs.  Fix that and improve
  the relevant comments.  Since this is mostly a comment fix, with
  only a rather marginal performance boost, no need for back-patch.
  Tom Lane and Dean Rasheed

- Be more paranoid about null return values from libpq status
  functions.  PQhost() can return NULL in non-error situations, namely
  when a Unix-socket connection has been selected by default.  That
  behavior is a tad debatable perhaps, but for the moment we should
  make sure that psql copes with it.  Unfortunately, do_connect()
  failed to: it could pass a NULL pointer to strcmp(), resulting in
  crashes on most platforms.  This was reported as a security issue by
  ChenQin of Topsec Security Team, but the consensus of the security
  list is that it's just a garden-variety bug with no security
  implications.  For paranoia's sake, I made the keep_password test
  not trust PQuser or PQport either, even though I believe those will
  never return NULL given a valid PGconn.  Back-patch to all supported

- Fix failure to consider failure cases in GetComboCommandId().
  Failure to initially palloc the comboCids array, or to realloc it
  bigger when needed, left combocid's data structures in an
  inconsistent state that would cause trouble if the top transaction
  continues to execute.  Noted while examining a user complaint about
  the amount of memory used for this.  (There's not much we can do
  about that, but it does point up that repalloc failure has a
  non-negligible chance of occurring here.) In HEAD/9.5, also avoid
  possible invocation of memcpy() with a null pointer in
  SerializeComboCIDState; cf commit 13bba0227.

- Improve PQhost() to return useful data for default Unix-socket
  connections.  Previously, if no host information had been specified
  at connection time, PQhost() would return NULL (unless you are on
  Windows, in which case you got "localhost").  This is an unhelpful
  definition for a couple of reasons: it can cause corner-case crashes
  in applications (cf commit c5ef8ce53d), and there's no well-defined
  way for applications to find out the socket directory path that's
  actually in use.  As an example of the latter problem, psql
  substituted DEFAULT_PGSOCKET_DIR for NULL in a couple of places, but
  this is subtly wrong because it's conceivable that psql is using a
  libpq shared library that was built with a different setting.
  Hence, change PQhost() to return DEFAULT_PGSOCKET_DIR when
  appropriate, and strip out the now-dead substitutions in psql.
  (There is still one remaining reference to DEFAULT_PGSOCKET_DIR in
  psql, in prompt.c, which I don't see a nice way to get rid of.  But
  it only controls a prompt abbreviation decision, so it seems
  noncritical.) Also update the docs for PQhost, which had never
  previously mentioned the possibility of a socket directory path
  being returned.  In passing fix the outright-incorrect code comment
  about PGconn.pgunixsocket.

- Auto-generate file header comments in Unicode mapping files.  Some
  of the Unicode/*.map files had identification comments added to
  them, evidently by hand.  Others did not.  Modify the generating
  scripts to produce these comments automatically, and update the
  generated files that lacked them.  This is just minor cleanup as a
  by-product of trying to verify that the *.map files can indeed be
  reproduced from authoritative data.  There are a depressingly large
  number that fail to reproduce from the claimed sources.  I have not
  touched those in this commit, except for the JIS 2004-related files
  which required only a single comment update to match.  Since this
  only affects comments, no need to consider a back-patch.

- Update UCS_to_GB18030.pl with info about origin of the reference

- Avoid doing encoding conversions by double-conversion via
  MULE_INTERNAL.  Previously, we did many conversions for Cyrillic and
  Central European single-byte encodings by converting to a related
  MULE_INTERNAL coding scheme before converting to the destination.
  This seems unnecessarily inefficient.  Moreover, if the conversion
  encounters an untranslatable character, the error message will
  confusingly complain about failure to convert to or from
  MULE_INTERNAL, rather than the user-visible encodings.  Worse still,
  this approach results in some completely unnecessary conversion
  failures; there are cases where the chosen MULE subset lacks
  characters that exist in both of the user-visible encodings, causing
  a conversion failure that need not occur.  This patch fixes the
  first two of those deficiencies by introducing a new local2local()
  conversion support subroutine for direct conversion between any two
  single-byte character sets, and adding new conversion tables where
  needed.  However, I generated the new conversion tables by testing
  PG 9.5's behavior, so that the actual conversion behavior is
  bug-compatible with previous releases; the only user-visible
  behavior change is that the error messages for conversion failures
  are saner.  Changes in the conversion behavior will probably ensue
  after discussion.  Interestingly, although this approach requires
  more tables, the .so files actually end up smaller (at least on my
  x86_64 machine); the tables are smaller than the management code
  needed for double conversion.  Per a complaint from Albe Laurenz.

Robert Haas pushed:

- Remove volatile qualifiers from bufmgr.c and freelist.c.  Prior to
  commit 0709b7ee72e4bc71ad07b7120acd117265ab51d0, access to variables
  within a spinlock-protected critical section had to be done through
  a volatile pointer, but that should no longer be necessary.  Review
  by Andres Freund

- Fix dumb bug in tqueue.c.  When I wrote this code originally, the
  intention was to recompute the remapinfo only when the tupledesc
  changes.  This presumably only happens once per query, but I copied
  the design pattern from other DestReceivers.  However, due to a
  silly oversight on my part, tqueue->tupledesc never got set, leading
  to recomputation for every tuple.  This should improve the
  performance of parallel scans that return a significant number of
  tuples.  Report by Amit Kapila; patch by me, reviewed by him.

- Avoid aggregating worker instrumentation multiple times.  Amit
  Kapila, per design ideas from me.

- Make a comment more precise.  Remote expressions now also matter to
  make_foreignscan() Noted by Etsuro Fujita.

- Fix incomplete set_foreignscan_references handling for
  fdw_recheck_quals KaiGai Kohei

- Make ALTER .. SET SCHEMA do nothing, instead of throwing an ERROR.
  This was already true for CREATE EXTENSION, but historically has not
  been true for other object types.  Therefore, this is a backward
  incompatibility.  Per discussion on pgsql-hackers, everyone seems to
  agree that the new behavior is better.  Marti Raudsepp, reviewed by
  Haribabu Kommi and myself

- Remove numbers from incorrectly-numbered list.  Reported by Andres

- Fix typo in comment.  Amit Langote

- Avoid server crash when worker registration fails at execution time.
  The previous coding attempts to destroy the DSM in this case, but
  child nodes might have stored data there and still be holding onto
  pointers in this case.  So don't do that.  Also, free the reader
  array instead of leaking it.  Extracted from two different patch
  versions both by Amit Kapila.

Peter Eisentraut pushed:

- doc: Fix commas and improve spacing

- Improve message

- Message style fix from Euler Taveira

- Message improvements

- doc: Clarify some things on pg_receivexlog reference page

- doc: Add more documentation about wal_retrieve_retry_interval from
  Michael Paquier

- doc: Some improvements on CREATE POLICY and ALTER POLICY

Andres Freund pushed:

- Remove function names from some elog() calls in heapam.c.  At least
  one of the names was, due to a function renaming late in the
  development of ON CONFLICT, wrong. Since including function names in
  error messages is against the message style guide anyway, remove
  them from the messages.  Discussion:
  CAM3SWZT8paz=usgMVHm0XOETkQvzjRtAUthATnmaHQQY0obnGw <at> mail.gmail.com
  Backpatch: 9.5, where ON CONFLICT was introduced

- Improve ON CONFLICT documentation.  Author: Peter Geoghegan and
  Andres Freund.  Discussion:
  CAM3SWZScpWzQ-7EJC77vwqzZ1GO8GNmURQ1QqDQ3wRn7AbW1Cg <at> mail.gmail.com
  Backpatch: 9.5, where ON CONFLICT was introduced

Andrew Dunstan pushed:

- Improve vcregress.pl's handling of tap tests for client programs The
  target is now named 'bincheck' rather than 'tapcheck' so that it
  reflects what is checked instead of the test mechanism. Some of the
  logic is improved, making it easier to add further sets of TAP based
  tests in future. Also, the environment setting logic is imrpoved.
  As discussed on -hackers a couple of months ago.

- Update docs for vcregress.pl bincheck changes

- fix a perl typo

Teodor Sigaev pushed:

- Clarify pg_rewind connection requirements.  Per
  http://www.postgresql.org/message-id/flat/564C4CE6.9000509 <at> postgrespro.ru
  Pavel Luzanov <p.luzanov <at> postgrespro.ru>

- Add forgotten file in commit

- Improve pageinspect module.  Now pageinspect can show data stored in
  the heap tuple.  Nikolay Shaplov

- COPY (INSERT/UPDATE/DELETE .. RETURNING ..) Attached is a patch for
  being able to do COPY (query) without a CTE.  Author: Marko Tiikkaja
  Review: Michael Paquier

Bruce Momjian pushed:

- pg_upgrade:  fix CopyFile() on Windows to fail on file existence
  Also fix getErrorText() to return the right error string on failure.
  This behavior now matches that of other operating systems.  Report
  by Noah Misch Backpatch through 9.1

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Álvaro Herrera sent in a patch to improve cost estimates for BRIN

Álvaro Herrera sent in a patch to fix some misbehavior of the
max_worker_processes GUC on standbys.

Peter Geoghegan sent in a patch to speed up CREATE INDEX

Kyotaro HORIGUCHI sent in a patch to improve the documentation of
floating point conversion for PL/pgsql.

Amit Kapila sent in two more revisions of a patch to speed up CLOG

Peter Eisentraut sent in a patch to play nicer with systemd.

Vitaly Burovoy sent in another revision of a patch to make fields
extracted from 'infinity' timestamp[tz]s sane.

Victor Wagner sent in another revision of a patch to implement
failover on the libpq connect level.

Amit Kapila sent in a patch to fix ExecParallelFinish() to be

Ildus Kurbangaliev sent in two revisions of a patch to slice bufmgr
into tranches similar to the way LWLocks are.

Robert Haas sent in a patch to tighten up how database names get
checked for in pg_basebackup.

Nikolay Shaplov sent in two more revisions of a patch to add tuple
data inspection to pageinspect.

Kyotaro HORIGUCHI sent in two revisions of a patch to add backend
regexp processing to psql's tab completion implementation.

Ashutosh Bapat and Rushabh Lathia traded patches to get sorted data
from a foreign server for merge join purposes.

SAWADA Masahiko sent in four more revisions of a patch to add a
"frozen" bit to the visibility map.

Thomas Munro sent in another revision of a patch to add "causal

Marko Tiikkaja sent in a patch to add a scale(numeric) function.

Marko Tiikkaja sent in a patch to add a trim(numeric) function.

Marko Tiikkaja sent in a PoC patch to implement "LISTEN *".

Amit Kapila sent in two revisions of a patch to fix an issue in
parallel seq scan with parallel worker allocation.

Michael Paquier and Stephen Frost traded patches to add new default

Robert Haas sent in another revision of a patch to implement parallel

Nikolay Shaplov sent in a patch to add a TAP test example.

Craig Ringer sent in another revision of a patch to implement
pg_logical, a general-purpose logical output plugin.

Marko Tiikkaja sent in two more revisions of a patch to add a
num_nulls() function.

Marko Tiikkaja sent in another revision of a patch to add a
single_value() aggregate.

Taiki Kondo and Kyotaro HORIGUCHI traded patches to improve query
performance by doing join pushdowns to table partitions.

Michael Paquier sent in two more revisions of a patch to add a
dedicated WAL record forcing fsync().

Andreas Karlsson sent in another revision of a patch to cause a SIGHUP
sent to the backend to reload SSL certificates.

Amit Langote sent in two revisions of a patch to fix some comments in

Haribabu Kommi sent in another revision of a patch to add a
pg_hba_lookup function to get all matching pg_hba.conf entries.

Pavel Stěhule sent in another revision of a patch to add a custom
function for converting human readable sizes to bytes.

Michael Paquier and Álvaro Herrera traded patches to add in-core
regression tests for replication, cascading, archiving, PITR, etc.

David Steele sent in a patch to enable client log output filtering.

Catalin Iacob sent in a patch to update the docs for the case when
psql is given multiple -c commands.

Pavel Stěhule sent in another revision of a patch to implement
multiple -c commands in psql.

Robert Haas sent in a patch to allow the optimizer to generate plans
where a Nested Loop or Hash Join appears below a Gather node and
improve the output of EXPLAIN when parallel workers are used.

Magnus Hagander and Michael Paquier traded patches to initialize more
parts of the walsnd structure.

Kaigai Kouhei sent in a patch to adds a Path *fdw_outerpath field to
the ForeignPath node.

Dean Rasheed sent in another revision of a patch to add trig functions
which take degrees as input.

Dmitry Ivanov sent in a patch to add a dump_stat extension which, as
implied in the name, allows dumping the contents of pg_statistic in a
form that lets it be reloaded.

Peter Geoghegan sent in a patch to ensure that GatherPath is within
print_path().  Not having it there prevented complete information from
appearing when using OPTIMIZER_DEBUG.

Tomas Vondra sent in some patches to fix a possible issue with fsync()
not actually being issued at the appropriate times.

Noah Misch sent in a patch to clarify some comments in

Pavel Stěhule sent in another revision of a patch to add an ereport()
function to PL/PythonU.

Peter Geoghegan sent in a patch to abort C collation text abbreviation
less frequently.


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

Satoshi Nagayasu | 26 Nov 08:33 2015

pgDay Asia 2016 and FOSSASIA 2016 - Announcement & Call for Presentations

Hi all,

We are please to announce the first pan-Asian PostgreSQL conference
in March 2016 in Singapore.


pgDay Asia is the PostgreSQL conference series for all PostgreSQL
enthusiasts in the Asia Pacific region.

pgDay Asia 2016 is a 2-day event linking to FOSSASIA 2016, one of the
largest FLOSS conferences in Asia.


So, you will be able to enjoy both the first Asian PostgreSQL
conference and one of the largest FLOSS conferences to meet new friends
in Asia in the same week!

Today, we open the pgDay Asia web site, and the Call for Presentations
just begins. Please submit your talks to share your experiences and meet
new friends in Asia.

And if you are interested in pgDay Asia, please subscribe to our list
to stay informed on the website. http://2016.pgday.asia/

*** Date ***

  March 17 and 19 (FOSSASIA 2016 will be held on March 18-20)

*** Venue **

  NUS Plug-In <at> Blk71, Singapore (and some hotel around NUS)

*** Call for Presentations ***

  2015-11-26:    Proposals acceptance begins
  Late-December: Proposals acceptance ends
  Mid-January:   Authors of accepted proposals contacted

All other information you need are available here:


Please visit our website, and let's meet many PG and FLOSS guys in

This conference is organized by the PostgreSQL people from Asian
communities (You can see the list on the web site).
If you have any question, feel free to ask me.

NAGAYASU Satoshi <snaga <at> uptime.jp>


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

Tomas Vondra | 24 Nov 12:02 2015

Prague PostgreSQL Developers Day 2016

Prague PostgreSQL Developer Day 2016 (P2D2 2016) is a two-day conference
that will be held on February 17-18 2016 in Prague, Czech Republic. The
venue will be announced in a few days.

The conference will have two parts:

trainings on Feb 17 - sessions on practical topics, for small number of
                       attendees (either half or whole day)

conference on Feb 18 - a regular conference (with ~45 minute talks for
                        large number of attendees).

The conference website is http://www.p2d2.cz/ (czech language only), but
feel free to contact us at info(at)p2d2(dot)cz in case of any questions.

The event is organized for local users, therefore most of the talks will
be presented in czech. However as in previous years, we're looking for a
few english-speaking guests, We can offer a subsidy covering travel and
hotel expenses up to ~500 EUR (should be enough for 2 nights in a hotel
and air ticket from around Europe).

If you'd like to present something interesing and related to
PostgreSQL at the  conference, send us some basic info at 
We especially need this:

  * contact info (name, phone, company)
  * topic of the session (abstract, what is the goal, etc.)
  * expected length (usually 40 minutes)
  * whether you need help with covering travel/hotel expenses

***** Schedule *****

The call for papers ends on January 11, 2016 (end of day). The talks
schedule will be announced till January 18 (and the registration will
open shortly after that).

***** Contacts *****

The conference is organized by Czech and Slovak PostgreSQL User Group.
In case of any questions, contact us at info(at)p2d2(dot)cz(dot)

kind regards
Tomas Vondra / CSPUG


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

Andreas 'ads' Scherbaum | 17 Nov 20:32 2015

FOSDEM PGDay and Devroom 2016 - Announcement & Call for Papers

FOSDEM PGDay is a one day conference that will be held ahead of FOSDEM 
in Brussels, Belgium, on Jan 29th, 2016. This will be a one-day focused 
PostgreSQL event, with a single track of talks. Registration is required 
to attend, the registration will open soon. Since we have a limited 
number of seats available for this event, we urge everybody to register 
as soon as possible once open.

PostgreSQL Europe will also have our regular devroom at FOSDEM on Sunday 
the 31st, which will be held at the main FOSDEM venue at ULB. This day 
will, of course, continue to be free of charge and open to all FOSDEM 
entrants. No registration is required to attend this day.

For full details about the conference, venue and hotel, see 
http://fosdem2016.pgconf.eu/ .

The call for papers is now open for both these events. We are looking 
for talks to fill both these days with content for both insiders and new 
users. Please see http://fosdem2016.pgconf.eu/callforpapers/ for details 
and submission information.

The deadline for submissions is December 7th, 2015, but we may as usual 
pre-approve some talks, so get your submissions in soon!

We will provide a special rate with the Brussels Marriott Hotel. For 
details, see http://fosdem2016.pgconf.eu/venue/ .

				Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project


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

Devrim GÜNDÜZ | 16 Nov 08:57 2015

PostgreSQL 9.6devel RPMs are ready for testing


PostgreSQL 9.6 is coming with some great features, and one of them is
parallel sequential scan:


To help people test all of upcoming features, I will push regularly
updated RPMs for the following platforms to the PostgreSQL YUM

* RHEL/CentOS/Scientific Linux/Oracle Enterprise Linux 6 and 7
* Fedora 23 and 22

Please note that these packages are built using the official daily
tarball. The package name contains the date that the package is built

More information can be found at:


These packages are for crash testing only, never ever intended for
production or even beta or alpha usage.

Please report any PostgreSQL bugs to pgsql-bugs <at> PostgreSQL.org 


Principal Systems Engineer  <at>  EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter:  <at> DevrimGunduz ,  <at> DevrimGunduzTR

Giulio Calacoci | 16 Nov 11:38 2015

Barman 1.5.1 released

16 November 2015: 2ndQuadrant is proud to announce the release of
version 1.5.1 of Barman, Backup and Recovery Manager for PostgreSQL.

This minor release introduces support for 'per-server' concurrency of
maintenance operations through the 'cron' command. Internally, Barman is
now able to spawn a new sub-process for WAL archive operations on a
specific server. For this purpose, the 'archive-wal' command has been
added to the command interface.

Minor bugs have also been fixed.

For a complete list of changes, see the "[Release Notes]" section below.


-   Man page, section 1: http://docs.pgbarman.org/barman.1.html
-   Man page, section 5: http://docs.pgbarman.org/barman.5.html

Release notes

-   Add support for the 'archive-wal' command which performs WAL
    maintenance operations on a given server
-   Add support for "per-server" concurrency of the 'cron' command
-   Improved management of xlog.db errors
-   Add support for mixed compression types in WAL files (SF.net#61)
-   Bug fixes:
    -   Avoid retention policy checks during the recovery
    -   Avoid 'wal_level' check on PostgreSQL version < 9.0 (#3)
    -   Fix backup size calculation (#5)


-   Release Notes:
-   Sources:
-   RPMs for RHEL/CentOS 5:
-   Barman:
-   Dependencies:
-   RPMs for RHEL/CentOS 6:
-   Barman:
-   Dependencies:
-   pgespresso on PostgreSQL Extension framework (PGXN):
-   pgespresso RPM/Debian packages:
-   Online documentation: http://www.pgbarman.org/documentation
-   PDF documentation:


Barman (Backup and Recovery Manager) is an open source administration
tool for disaster recovery of PostgreSQL servers written in Python. It
allows your organisation to perform remote backups of multiple servers
in business critical environments and help DBAs during the recovery
phase. Barman's most requested features include backup catalogues,
incremental backup, retention policies, remote backup and recovery,
archiving and compression of WAL files and backups. Barman is
distributed under GNU GPL 3.

 Giulio Calacoci - 2ndQuadrant Italia
 PostgreSQL Training, Services and Support
 giulio.calacoci <at> 2ndQuadrant.it | www.2ndQuadrant.it 
David Fetter | 16 Nov 08:01 2015

== PostgreSQL Weekly News - November 15 2015 ==

== PostgreSQL Weekly News - November 15 2015 ==

PostgreSQL 9.5 Beta 2 released.  Test!

== PostgreSQL Product News ==

pg_wintools, a PostgreSQL extension for interfacing with Windows OS,

== PostgreSQL Jobs for November ==


== PostgreSQL Local ==

PGConf Silicon Valley 2015 is November 17-18 at the South San
Francisco Convention Center.

PGBR2015 (The Brazilian PostgreSQL Conference) will take place in Porto
Alegre, Rio Grande do Sul, on November 18, 19 and 20.  Registration is

Postgres Conference China 2015 will be on November 20-22, 2015 in
http://postgres2015.eventdove.com/   (Chinese)
http://postgrescluster2015.eventdove.com/ (English)

PGConf.DE will be held on November 26-27, 2015 in Hamburg, Germany, at
the Lindner Hotel am Michel.

PostgreSQL <at> SCaLE is a two day, two track event which takes place on Jan.
21-22, 2016, at Pasadena Convention Center, as part of SCaLE 14X.

== 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 ==

Andres Freund pushed:

- Add paragraph about ON CONFLICT interaction with partitioning.
  Author: Peter Geoghegan and Andres Freund Discussion:
  CAM3SWZScpWzQ-7EJC77vwqzZ1GO8GNmURQ1QqDQ3wRn7AbW1Cg <at> mail.gmail.com,
  CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q <at> mail.gmail.com
  Backpatch: 9.5, where UPSERT was introduced

Robert Haas pushed:

- Add a dummy return statement to TupleQueueRemap.  This is
  unreachable for multiple reasons, but per Amit Kapila the Windows
  compiler he is using still thinks we can get there.

- Fix rebasing mistake in nodeGather.c The patches committed as
  6e71dd7ce9766582da453f493bc371d64977282f and
  3a1f8611f2582df0a16bcd35caed2e1526387643 were developed in parallel
  but dependent on each other in a way that I failed to notice.  This
  patch to fix the problem was prepared by Amit Kapila.

- Comment update.  Adjust to account for
  5fc4c26db5120bd90348b6ee3101fcddfdf54800.  Etsuro Fujita

- Add outfuncs.c support for GatherPath.  I dunno how commit
  3bd909b220930f21d6e15833a17947be749e7fde missed this, but it
  evidently did.

- Make sequential scans parallel-aware.  In addition, this path fills
  in a number of missing bits and pieces in the parallel
  infrastructure.  Paths and plans now have a parallel_aware flag
  indicating whether whatever parallel-aware logic they have should be
  engaged.  It is believed that we will need this flag for a number of
  path/plan types, not just sequential scans, which is why the flag is
  generic rather than part of the SeqScan structures specifically.
  Also, execParallel.c now gives parallel nodes a chance to initialize
  their PlanState nodes from the DSM during parallel worker startup.
  Amit Kapila, with a fair amount of adjustment by me.  Review of
  previous patch versions by Haribabu Kommi and others.

- Generate parallel sequential scan plans in simple cases.  Add a new
  flag, consider_parallel, to each RelOptInfo, indicating whether a
  plan for that relation could conceivably be run inside of a parallel
  worker.  Right now, we're pretty conservative: for example, it might
  be possible to defer applying a parallel-restricted qual in a
  worker, and later do it in the leader, but right now we just don't
  try to parallelize access to that relation.  That's probably the
  right decision in most cases, anyway.  Using the new flag, generate
  parallel sequential scan plans for plain baserels, meaning that we
  now have parallel sequential scan in PostgreSQL.  The logic here is
  pretty unsophisticated right now: the costing model probably isn't
  right in detail, and we can't push joins beneath Gather nodes, so
  the number of plans that can actually benefit from this is pretty
  limited right now.  Lots more work is needed.  Nevertheless, it
  seems time to enable this functionality so that all this code can
  actually be tested easily by users and developers.  Note that, if
  you wish to test this functionality, it will be necessary to set
  max_parallel_degree to a value greater than the default of 0.  Once
  a few more loose ends have been tidied up here, we might want to
  consider changing the default value of this GUC, but I'm leaving it
  alone for now.  Along the way, fix a bug in cost_gather: the
  previous coding thought that a Gather node's transfer overhead
  should be costed on the basis of the relation size rather than the
  number of tuples that actually need to be passed off to the leader.
  Patch by me, reviewed in earlier versions by Amit Kapila.

- Provide readfuncs support for custom scans.  Commit
  a0d9f6e434bb56f7e5441b7988f3982feead33b3 added this support for all
  other plan node types; this fills in the gap.  Since
  TextOutCustomScan complicates this and is pretty well useless,
  remove it.  KaiGai Kohei, with some modifications by me.

- Make idle backends exit if the postmaster dies.  Letting backends
  continue to run if the postmaster has exited prevents PostgreSQL
  from being restarted, which in many environments is catastrophic.
  Worse, if some other backend crashes, we no longer have any
  protection against shared memory corruption.  So, arrange for them
  to exit instead.  We don't want to expend many cycles on this, but
  including postmaster death in the set of things that we wait for
  when a backend is idle seems cheap enough.  Rajeev Rastogi and
  Robert Haas

- Move each SLRU's lwlocks to a separate tranche.  This makes it
  significantly easier to identify these lwlocks in LWLOCK_STATS or
  Trace_lwlocks output.  It's also arguably better from a modularity
  standpoint, since lwlock.c no longer needs to know anything about
  the LWLock needs of the higher-level SLRU facility.  Ildus
  Kurbangaliev, reviewd by Álvaro Herrera and by me.

- libpq: Notice errors a backend may have sent just before dying.  At
  least since the introduction of Hot Standby, the backend has
  sometimes sent fatal errors even when no client query was in
  progress, assuming that the client would receive it.  However,
  pqHandleSendFailure was not in sync with this assumption, and only
  tries to catch notices and notifies.  Add a parseInput call to the
  loop there to fix.  Andres Freund suggested the fix.  Comments are
  by me.  Reviewed by Michael Paquier.

- Remove accidentally-committed debugging code.  Amit Kapila

Tom Lane pushed:

- Improve our workaround for 'TeX capacity exceeded' in building PDF
  files.  In commit a5ec86a7c787832d28d5e50400ec96a5190f2555 I wrote a
  quick hack that reduced the number of TeX string pool entries
  created while converting our documentation to PDF form.  That held
  the fort for awhile, but as of HEAD we're back up against the same
  limitation.  It turns out that the original coding of
  \FlowObjectSetup actually results in *three* string pool entries
  being generated for every "flow object" (that is, potential
  cross-reference target) in the documentation, and my previous hack
  only got rid of one of them.  With a little more care, we can reduce
  the string count to one per flow object plus one per
  actually-cross-referenced flow object (about 115000 + 5000 as of
  current HEAD); that should work until the documentation volume
  roughly doubles from where it is today.  As a not-incidental side
  benefit, this change also causes pdfjadetex to stop emitting
  unreferenced hyperlink anchors (bookmarks) into the PDF file.  It
  had been making one willy-nilly for every flow object; now it's just
  one per actually-cross-referenced object.  This results in close to
  a 2X savings in PDF file size.  We will still want to run the output
  through "jpdftweak" to get it to be compressed; but we no longer
  need removal of unreferenced bookmarks, so we might be able to find
  a quicker tool for that step.  Although the failure only affects
  HEAD and US-format output at the moment, 9.5 cannot be more than a
  few pages short of failing likewise, so it will inevitably fail
  after a few rounds of minor-version release notes.  I don't have a
  lot of faith that we'll never hit the limit in the older branches;
  and anyway it would be nice to get rid of jpdftweak across the
  board.  Therefore, back-patch to all supported branches.

- Add missing "static" qualifier.  Per buildfarm member pademelon.

- Docs: fix misleading example.  Commit 8457d0beca731bf0 introduced an
  example which, while not incorrect, failed to exhibit the behavior
  it meant to describe, as a result of omitting an E'' prefix that
  needed to be there.  Noticed and fixed by Peter Geoghegan.  I (tgl)
  failed to resist the temptation to wordsmith nearby text a bit while
  at it.

- Be more noisy about "wrong number of nailed relations" initfile
  problems.  In commit 5d1ff6bd559ea8df1b7302e245e690b01b9a4fa4 I
  added some logic to relcache.c to try to ensure that the regression
  tests would fail if we made a mistake about which relations belong
  in the relcache init files.  I'm quite sure I tested that, but I
  must have done so only for the non-shared-catalog case, because a
  report from Adam Brightwell showed that the regression tests still
  pass just fine if we bollix the shared-catalog init file in the way
  this code was supposed to catch.  The reason is that that file gets
  loaded before we do client authentication, so the WARNING is not
  sent to the client, only to the postmaster log, where it's far too
  easily missed.  The least Rube Goldbergian answer to this is to put
  an Assert(false) after the elog(WARNING).  That will certainly get
  developers' attention, while not breaking production builds' ability
  to recover from corner cases with similar symptoms.  Since this is
  only of interest to developers, there seems no need for a
  back-patch, even though the previous commit went into all branches.

- Improve documentation around autovacuum-related storage parameters.
  These were discussed in three different sections of the manual,
  which unsurprisingly had diverged over time; and the descriptions of
  individual variables lacked stylistic consistency even within each
  section (and frequently weren't in very good English anyway).  Clean
  up the mess, and remove some of the redundant information in hopes
  that future additions will be less likely to re-introduce
  inconsistency.  For instance I see no need for maintenance.sgml to
  include its very own list of all the autovacuum storage parameters,
  especially since that list was already incomplete.

- Do a round of copy-editing on the 9.5 release notes.  Also fill in
  the previously empty "major enhancements" list.  YMMV as to which
  items should make the cut, but it's past time we had something more
  than a placeholder here.  (I meant to get this done before beta2 was
  wrapped, but got distracted by PDF build problems.  Better late than

- Fix unwanted flushing of libpq's input buffer when socket EOF is
  seen.  In commit 210eb9b743c0645d I centralized libpq's logic for
  closing down the backend communication socket, and made the new
  pqDropConnection routine always reset the I/O buffers to empty.
  Many of the call sites previously had not had such code, and while
  that amounted to an oversight in some cases, there was one place
  where it was intentional and necessary *not* to flush the input
  buffer: pqReadData should never cause that to happen, since we
  probably still want to process whatever data we read.  This is the
  true cause of the problem Robert was attempting to fix in
  c3e7c24a1d60dc6a, namely that libpq no longer reported the backend's
  final ERROR message before reporting "server closed the connection
  unexpectedly".  But that only accidentally fixed it, by invoking
  parseInput before the input buffer got flushed; and very likely
  there are timing scenarios where we'd still lose the message before
  processing it.  To fix, pass a flag to pqDropConnection to tell it
  whether to flush the input buffer or not.  On review I think
  flushing is actually correct for every other call site.  Back-patch
  to 9.3 where the problem was introduced.  In HEAD, also improve the
  comments added by c3e7c24a1d60dc6a.

- Improve type numeric's calculations for ln(), log(), exp(), pow().
  Set the "rscales" for intermediate-result calculations to ensure
  that suitable numbers of significant digits are maintained
  throughout.  The previous coding hadn't thought this through in any
  detail, and as a result could deliver results with many inaccurate
  digits, or in the worst cases even fail with divide-by-zero errors
  as a result of losing all nonzero digits of intermediate results.
  In exp_var(), get rid entirely of the logic that separated the
  calculation into integer and fractional parts: that was neither
  accurate nor particularly fast.  The existing range-reduction method
  of dividing by 2^n can be applied across the full input range
  instead of only 0..1, as long as we are careful to set an
  appropriate rscale for each step.  Also fix the logic in mul_var()
  for shortening the calculation when the caller asks for fewer output
  digits than an exact calculation would require.  This bug doesn't
  affect simple multiplications since that code path asks for an exact
  result, but it does contribute to accuracy issues in the
  transcendental math functions.  In passing, improve performance of
  mul_var() a bit by forcing the shorter input to be on the left, thus
  reducing the number of iterations of the outer loop and probably
  also reducing the number of carry-propagation steps needed.  This is
  arguably a bug fix, but in view of the lack of field complaints, it
  does not seem worth the risk of back-patching.  Dean Rasheed

- Fix ruleutils.c's dumping of whole-row Vars in ROW() and VALUES()
  contexts.  Normally ruleutils prints a whole-row Var as "foo.*".  We
  already knew that that doesn't work at top level of a SELECT list,
  because the parser would treat the "*" as a directive to expand the
  reference into separate columns, not a whole-row Var.  However,
  Joshua Yanovski points out in bug #13776 that the same thing happens
  at top level of a ROW() construct; and some nosing around in the
  parser shows that the same is true in VALUES().  Hence, apply the
  same workaround already devised for the SELECT-list case, namely to
  add a forced cast to the appropriate rowtype in these cases.  (The
  alternative of just printing "foo" was rejected because it is
  difficult to avoid ambiguity against plain columns named "foo".)
  Back-patch to all supported branches.

Álvaro Herrera pushed:

- vacuumdb: don't prompt for passwords over and over.  Having the
  script prompt for passwords over and over was a preexisting problem
  when it processed multiple databases or when it processed multiple
  analyze stages, but the parallel mode introduced in commit
  a179232047 made it worse.  Fix the annoyance by keeping a copy of
  the password used by the first connection that requires one.  Since
  users can (currently) only have a single password, there's no need
  for more complex arrangements (such as remembering one password per
  database).  Per bug #13741 reported by Eric Brown.  Patch authored
  and cross-reviewed by Haribabu Kommi and Michael Paquier, slightly
  tweaked by Álvaro Herrera.  Discussion:
  http://www.postgresql.org/message-id/20151027193919.931.54948 <at> wrigleys.postgresql.org
  Backpatch to 9.5, where parallel vacuumdb was introduced.

Stephen Frost pushed:

- Correct sepgsql docs with regard to RLS The sepgsql docs included a
  comment that PG doesn't support RLS.  That is only true for versions
  prior to 9.5.  Update the docs for 9.5 and master to say that PG
  supports RLS but that sepgsql does not yet.  Pointed out by Heikki.
  Back-patch to 9.5

Bruce Momjian pushed:

- pg_upgrade:  properly detect file copy failure on Windows.
  Previously, file copy failures were ignored on Windows due to an
  incorrect return value check.  Report by Manu Joye Backpatch through

- Fix spelling error in postgresql.conf.  Report by Greg Clough

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Adam Brightwell sent in two revisions of a patch to bootstrap
pg_shseclabel in relcache initialization.

Kaigai Kouhei sent in another revision of a patch to reconcile Foreign
join pushdown with EvalPlanQual.

Ashutosh Bapat sent in another revision of a patch to add a
transaction manager for foreign servers.

Marco Nenciarini sent in a patch to fix an incompatibility between
9.3's WAL stream and pg_receivelog.

Kaigai Kouhei sent in a patch for each of 9.5 and git master to allow
CustomScan on copyfuncs.

Pavel Stěhule sent in another revision of a patch to allow psql to
send multiple SQL statements via the command line.

Pavel Stěhule and Catalin Iacob traded patches to add an ereport
function to PL/PythonU.

Artur Zakirov sent in another revision of a patch to enhance the
performance of Hunspell dictionaries in full-text search.

Peter Geoghegan sent in a patch to fix some erroneous documentation of

Michael Paquier sent in another revision of a patch to add
trigonometric functions which take degree values as input.

Andres Freund sent in another revision of a patch to control
continuous flushing of checkpoints.

Thomas Munro sent in two revisions of a patch to create a "causal
reads" capability.

Peter Eisentraut sent in another revision of a patch to handle missing
pieces of compilation infrastructure more gracefully.

Michael Paquier sent in another revision of a patch to show tuple data
in pageinspect.

Craig Ringer sent in a patch to implement pg_logical, a plugin based
on logical WAL streams.

Kyotaro HORIGUCHI sent in a patch to allow using regexes in frontend
code, in particular tab completion for psql.

Thomas Munro sent in another revision of a patch to simplify tab
completion in psql.

Alexander Korotkov sent in another revision of a patch to rework the
access method interface.

Peter Geoghegan sent in a patch to expand SortSupport to char(n),
bytea, and alternative opclasses.

Kaigai Kouhei sent in a patch to add serialization support to

SAWADA Masahiko sent in two more revisions of a patch to add a
"frozen" bit to the visibility map.

Amit Kapila sent in a patch to fix an issue in the parallel seq scan

Robert Haas sent in a patch to implement Append in parallel.

Jeff Janes and Tom Lane traded patches to speed up set_rtable_names.

Amit Kapila sent in a patch to fix some issues in parallel seq scan.

Robert Haas sent in a patch to tranche-ify buffer locks.

Haribabu Kommi sent in another revision of a patch to skip ALTER x SET
SCHEMA if the schema didn't change.


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

Dave Page | 12 Nov 20:15 2015

PostgreSQL 9.5 Beta 2 Released

The PostgreSQL Global Development Group announces today that the
second beta release of PostgreSQL 9.5 is available for download. This
release should contain all features and APIs which will be in the
final release with few, if any, changes. Users should begin testing
their applications against 9.5 Beta 2 in preparation for the final

Changes Since Beta1

Many bugs and issues reported by our users and contributors have been
fixed since the release of Beta1.  These include:

* Many documentation fixes and improvements
* Rename PQsslAttributes() to PQsslAttributeNames()
* Pass extra data to pgworkers for context
* Fix other issues with parallel workers
* Fix multiple issues with BRIN indexes
* Fix problems with commit timestamps and replication
* Put back ssl_renegotiation_limit, set to 0

If you reported an issue while testing PostgreSQL 9.5, please download
Beta2 and test whether that issue has been fixed.  If you have not yet
tested version 9.5, now is the time for you to help out PostgreSQL
development.  Known issues which are still open are listed on the Open
Items page.

Beta Schedule

This is second beta release of version 9.5, indicating that very few
user-visible feature changes are expected before final release.  The
PostgreSQL Project will release additional betas as required for
testing, followed by one or more release candidates, until the final
release in late 2015.  For more information, and suggestions on how to
test the betas, see the Beta Testing page.

Full documentation and release notes of the new version is available
online and also installs with PostgreSQL.  Also see the What's New
page for details on some features.


* Downloads Page: http://www.postgresql.org/download/
* Beta Testing Information: http://www.postgresql.org/developer/beta
* 9.5 eta Release Notes:
* What's New in 9.5:
* 9.5 Open Items: https://wiki.postgresql.org/wiki/PostgreSQL_9.5_Open_Items

Dave Page
PostgreSQL Core Team


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