delta/postgresql.git, branch REL9_6_BETA1

Stamp 9.6beta1.

2016-05-09T20:47:49+00:00

Translation updates

2016-05-09T14:04:41+00:00

Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 17bf3e8564abf600274789fcc90e72532d5e7c05

Improve 9.6 release notes.

2016-05-08T20:53:55+00:00

Incorporate some suggestions from David Johnston, and update through today.

Docs: create some user-facing documentation about index-only scans.

2016-05-08T20:36:19+00:00

We didn't have any real user documentation about how index-only scans
work or how to design indexes to exploit them.  Remedy that.
Per gripe from David Johnston.

Wording quibbles regarding initdb username

2016-05-08T16:58:21+00:00

Use disallowed instead of reserved, cannot instead of can not, and
double quotes instead of single quotes.

Also add a test to cover the bug which started this discussion.

Per discussion with Tom.

Disallow superuser names starting with 'pg_' in initdb

2016-05-08T15:55:44+00:00

As with CREATE ROLE, disallow users from specifying initial
superuser names which begin with 'pg_' in initdb.

Per discussion with Tom.

Fix poorly-worded log message.

2016-05-08T05:37:07+00:00

Euler Taveira

Release notes for 9.5.3, 9.4.8, 9.3.13, 9.2.17, 9.1.22.

2016-05-07T21:26:23+00:00

In new pg_dump TAP tests, remove trailing "$" from regexps using /m.

2016-05-07T20:36:50+00:00

It emerges that some Perl versions before 5.8.9 have a bug with regexps
that use the /m flag and contain "$".  This is the reason why jacana
is still failing on HEAD, and I was able to duplicate the failure on
prairiedog's host.  There's no real need for "$" in these patterns,
since they are already matching through the statement-terminating
semicolons (or matching an explicit \n in some cases).  So just
remove it.

Note: the reason jacana hasn't actually reported any failures in the
last little while is that the way the pg_dump TAP tests are set up, any
failure of this sort results in echoing the entire pg_dump dump output
to stderr.  Since there were about a hundred such failures, that resulted
in a 30MB log file which choked the buildfarm upload script.  There is
room for improvement here :-(.

Per off-list discussion with Andrew and Stephen.

Docs: improve warnings about nextval() not producing gapless sequences.

2016-05-07T17:16:50+00:00

In the documentation for nextval(), point out explicitly that INSERT ...
ON CONFLICT will call nextval() if needed for the insertion case, whether
or not it ends up following the ON CONFLICT path.  This seems to be a
matter of some confusion, cf bug #14126, so let's be clear about it.

Also mention the issue in the CREATE SEQUENCE reference page, since that
is another place where people might expect such things to be covered.

Minor wording improvements nearby, as well.

Back-patch to 9.5 where ON CONFLICT was introduced.