== PostgreSQL Weekly News - August 21 2016 ==
== PostgreSQL Jobs for August ==
http://archives.postgresql.org/pgsql-jobs/2016-08/threads.php
== PostgreSQL Local ==
PostgresOpen 2016 in will be held in Dallas, Texas September 13-16.
https://2016.postgresopen.org/
PostgreSQL Session will be held on September 22th, 2016, in Lyon,
France.
http://blog.dalibo.com/2016/05/13/CFP-pgsession-lyon.html
Postgres Vision 2016 will be held October 11-13, 2016, in San Francisco.
http://postgresvision.com/
PostgreSQL Conference Europe will take place in Tallin, Estonia, on
November 1-4, 2016. Early bird registration is open until September
14th, 2016.
http://2016.pgconf.eu/registration/
PgConf Silicon Valley 2016 will be held on November 14-16, 2016.
http://www.pgconfsv.com/
CHAR(16) will take place in New York, December 6, 2016. Call for
papers is open until midnight (EDT) September 13, 2016.
http://charconference.org/
== 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 da...@fetter.org, German language
to p...@pgug.de, Italian language to p...@itpug.org.
== Applied Patches ==
Tom Lane pushed:
- Simplify the process of perltidy'ing our Perl files. Wrap the
perltidy invocation into a shell script to reduce the risk of
copy-and-paste errors. Include removal of *.bak files in the
script, so they don't accidentally get committed. Improve the
directions in the README file.
http://git.postgresql.org/pg/commitdiff/05d8dec690e9719ff9a1830f5492864104275b5e
- Final pgindent + perltidy run for 9.6.
http://git.postgresql.org/pg/commitdiff/b5bce6c1ec6061c8a4f730d927e162db7e2ce365
- Stamp HEAD as 10devel. This is a good bit more complicated than the
average new-version stamping commit, because it includes various
adjustments in pursuit of changing from three-part to two-part
version numbers. It's likely some further work will be needed
around that change; but this is enough to get through the regression
tests, at least in Unix builds. Peter Eisentraut and Tom Lane
http://git.postgresql.org/pg/commitdiff/ca9112a424ff68ec4f2ef67b47122f7d61412964
- Stamp shared-library minor version numbers for v10.
http://git.postgresql.org/pg/commitdiff/0b9358d4406b9b45a06855d53f491cc7ce9550a9
- Update git_changelog to know that there's a 9.6 branch. Missed this
in the main 10devel version stamping patch.
http://git.postgresql.org/pg/commitdiff/3149a12166120d0b476f5ca7837ebcf0e7124703
- Allow .so minor version numbers above 9 in .gitignore. Needed now
that libpq.so's minor version has reached 10.
http://git.postgresql.org/pg/commitdiff/2bf06f756142f4c398270cdc30bbba9b9dfbd38b
- Doc: remove out-of-date claim that pg_am rows must be inserted by
hand. Commit 473b93287 added a sentence about that, but neglected
to remove the adjacent sentence it had falsified. Per Alexander
Law.
http://git.postgresql.org/pg/commitdiff/8fc571b7dd9fa1659536a26bb085584b50a65a51
- Doc: copy-editing in create_access_method.sgml. Improve shaky
English grammar. And markup.
http://git.postgresql.org/pg/commitdiff/9b002cc9fec557fcfe17d67f55b53804447230e5
- Remove separate version numbering for ecpg preprocessor. Once upon
a time, it made sense for the ecpg preprocessor to have its own
version number, because it used a manually-maintained grammar that
wasn't always in sync with the core grammar. But those days are
thankfully long gone, leaving only a maintenance nuisance behind.
Let's use the PG v10 version numbering changeover as an excuse to
get rid of the ecpg version number and just have ecpg identify
itself by PG_VERSION. From the user's standpoint, ecpg will go from
"4.12" in the 9.6 branch to "10" in the 10 branch, so there's no
failure of monotonicity. Discussion:
<1471332659.4410.67.ca...@postgresql.org>
http://git.postgresql.org/pg/commitdiff/a7b5573d665c8a37fad9bc69f44c5b4e8760a73b
- Automate the maintenance of SO_MINOR_VERSION for our shared
libraries. Up to now we've manually adjusted these numbers in
several different Makefiles at the start of each development cycle.
While that's not much work, it's easily forgotten, so let's get rid
of it by setting the SO_MINOR_VERSION values directly from
$(MAJORVERSION). In the case of libpq, this dev cycle's value of
SO_MINOR_VERSION happens to be "10" anyway, so this switch is
transparent. For ecpg's shared libraries, this will result in
skipping one or two minor version numbers between v9.6 and v10,
which seems like no big problem; and it was a bit inconsistent that
they didn't have equal minor version numbers anyway. Discussion:
<21969.1471287...@sss.pgh.pa.us>
http://git.postgresql.org/pg/commitdiff/a3bce17ef1ca6408e8d1e7b10fb767aef1729be6
- Fix assorted places in psql to print version num
