== PostgreSQL Weekly News - August 14 2017 ==
PostgreSQL 10 Beta 3 released. Test!
https://www.postgresql.org/about/news/1771/
Security releases 9.6.4, 9.5.8, 9.4.13, 9.3.18 and 9.2.22 are out. Please read
the announcement below and upgrade at the next available downtime.
https://www.postgresql.org/about/news/1772/
2ndQuadrant PostgreSQL Conference 2017 (2Q PGConf, for short) will be hosted on
November 6th & 7th in New York City, and November 9th in Chicago.
http://www.2qpgconf.com/
PGConf Local: Seattle Has been rescheduled to November 13 - 14, 2017.
Registration at https://www.pgconf.us/#Seattle2017
PGConf Local: Austin will be held December 4 - 5, 2017. Call for Papers is
now open at https://www.pgconf.us/conferences/Austin2017
== PostgreSQL Product News ==
PGroonga 1.2.3, a full text search platform for all languages, released.
http://groonga.org/en/blog/2017/07/03/pgroonga-1.2.3.html
JDBC 42.1.4 released
https://jdbc.postgresql.org/documentation/changelog.html#version_42.1.4
psqlODBC 09.06.0410 released.
https://odbc.postgresql.org/docs/release.html
psycopg2 2.7.3, a Python connector for PostgreSQL, released.
http://initd.org/psycopg/articles/2017/07/24/psycopg-273-released/
pg_repack 1.4.1, an extension for removing bloat, released.
http://reorg.github.io/pg_repack/
== PostgreSQL Jobs for August ==
http://archives.postgresql.org/pgsql-jobs/2017-08/
== PostgreSQL Local ==
PostgresOpen will occur September 6-8, 2017 in San Francisco.
https://2017.postgresopen.org/
PGBR2017 will take place in Porto Alegre, Rio Grande do Sul,
Brazil on September 14-16 2017.
https://pgbr.postgresql.org.br/2017/
PGDay.IT 2017 will take place in October 13th, in Milan, Italy.
http://pgday.it
PostgreSQL Conference Europe 2017 will be held on October 24-27, 2017 in the
Warsaw Marriott Hotel, in Warsaw, Poland.
https://2017.pgconf.eu/
PGConf Local: Seattle will be held November 13 - 14, 2017.
https://www.pgconf.us/#Seattle2017
PGDay Austin 2017 will be held on December 4 - 5, 2017.
https://pgdayaustin2017.postgresql.us
PGConf.ASIA 2017 will take place on December 4-6 2017 in Akihabara, Tokyo,
Japan.
http://www.pgconf.asia/EN/2017/
== 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 ==
Noah Misch pushed:
- Disclaim xmltable() support for non-UTF8 databases. The xmltable()
implementation mirrors xpath(), including its lack of character encoding
awareness.
https://git.postgresql.org/pg/commitdiff/b4a2eea030ba74ea84335c7d5bc999f693ffd9a4
- Fix vertical spanning in table "wait_event Description". Michael Paquier
Discussion:
https://postgr.es/m/cab7npqqr3keqvxeuunycm7tdk2fb9oluq8du0+y0rzeon_1...@mail.gmail.com
https://git.postgresql.org/pg/commitdiff/e88928c50dfe2623c899f82b54aad69da248ad07
Álvaro Herrera pushed:
- Fix replication origin-related race conditions. Similar to what was fixed in
commit 9915de6c1cb2 for replication slots, but this time it's related to
replication origins: DROP SUBSCRIPTION attempts to drop the replication
origin, but that fails if the replication worker process hasn't yet marked it
unused. This causes failures in the buildfarm: ERROR: could not drop
replication origin with OID 1, in use by PID 34069 Like the aforementioned
commit, fix by having the process running DROP SUBSCRIPTION sleep until the
worker marks the the replication origin struct as free. This uses a condition
variable on each replication origin shmem state struct, so that the session
trying to drop can sleep and expect to be awakened by the process keeping the
origin open. Also fix a SGML markup in the previous commit. Discussion:
https://postgr.es/m/20170808001433.rozlseaf4m2wkw3n@alvherre.pgsql
https://git.postgresql.org/pg/commitdiff/b2c95a3798ff39fc24d71b6655ddfe0e4cb3f378
- Fix inadequacies in recently added wait events In commit 9915de6c1cb2, we
introduced a new wait point for replication slots and incorrectly labelled it
as wait event PG_WAIT_LOCK. That's wrong, so invent an appropriate new wait
event instead, and document it properly. While at it, fix numerous other
problems in the vicinity: - two different walreceiver wait events were being
mixed up in a single wait event (which wasn't documented either); split it out
so that they can be distinguished, and document the new events properly. -
ParallelBitmapPopulate was documented but didn't exist. - ParallelBitmapScan
was not documented (I think this should be called "ParallelBitmapScanInit"
instead.) - Logical replication wait events weren't documented - various
symbols had been added in dartboard order in various places. Put them in
alphabetical order instead, as was originally i
