== PostgreSQL Weekly News - April 12 2015 ==
The 4th Turkish PostgreSQL Conference will be held on May 9, 2015 in
Istanbul.
http://pgday.postgresql.org.tr/en/index.html
== PostgreSQL Product News ==
pgbouncer 1.5.5, a light-weight connection pooler for PostgreSQL, released.
https://pgbouncer.github.io/downloads/
pgpool-II versions 3.4.2, 3.3.6, 3.2.11, 3.1.14, and 3.0.17 released.
pgpool-II is a connection pooler and replication system for PostgreSQL.
http://pgpool.net/mediawiki/index.php/Downloads
== PostgreSQL Jobs for April ==
http://archives.postgresql.org/pgsql-jobs/2015-04/threads.php
== PostgreSQL Local ==
The second Swiss Postgres Conference will be held June 25-26, 2015 at
HSR Rapperswil.
http://www.postgres-conference.ch/
There is a Postgres track in a database technology conference(DTCC) in
April 18, 2015 in Beijing, China.
http://dtcc.it168.com/list_jiabin.html
pgDay Paris will be held in Paris France on April 21, 2015.
http://pgday.paris/
Call for Papers for PGDay in Belfort, France ends April 13, 2015.
The conference will be held June 2, 2015.
http://select-2-6-2015-as-pgday.org
PGCon 2015 is June 16-20 in Ottawa, Canada.
http://www.pgcon.org/2015/
PGDay UK, Conference will be taking place on 7th July 2015 – it is aimed at
the UK PostgreSQL Community. The CfP is open until 13 April 2015.
http://www.postgresqlusergroup.org.uk
The Call For Papers for PostgresOpen 2015, being held in Dallas, Texas
from September 16th to 18th, is now open.
http://2015.postgresopen.org/callforpapers/
== 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. Spanish language
to p...@arpug.com.ar.
== Applied Patches ==
Fujii Masao pushed:
- Fix typo in libpq.sgml. Back-patch to all supported versions.
Michael Paquier
http://git.postgresql.org/pg/commitdiff/5f6a9d056a3ba8ba66cace5d84e46caadc6e3a42
- Add file_ops.c to GETTEXT_FILES in nls.mk. Since file_ops.c
contains translatable strings, it should have been listed in
GETTEXT_FILES.
http://git.postgresql.org/pg/commitdiff/29407f97746ba2543b1845afe8ae22af09d43e45
- Fix typo in comment.
http://git.postgresql.org/pg/commitdiff/026fafde9159046ad26d0ccba92be0e802c70e92
- Remove obsolete FORCE option from REINDEX. FORCE option has been
marked obsolete since very old version 7.4 but existed for
backwards compatibility. Per discussion on pgsql-hackers, we
concluded that it's no longer worth keeping supporting the option.
http://git.postgresql.org/pg/commitdiff/17d436d2e894a91f3e8a9eb1bb1688cb515f1546
- Mark the second argument of pg_log as the translatable string in
nls.mk.
http://git.postgresql.org/pg/commitdiff/b216ad7bf1a9308c97d2032d4793010e8c8aa7ec
Álvaro Herrera pushed:
- Fix object identities for pg_conversion objects. This was already
fixed in 0d906798f, but I failed to update the array-formatted case.
This is not backpatched, since this only affects the code path
introduced by commit a676201490c.
http://git.postgresql.org/pg/commitdiff/70dc2db7f1dfdecdacf595bf00964cb20ad5a835
- pg_event_trigger_dropped_objects: add is_temp column. It now also
reports temporary objects dropped that are local to the backend.
Previously we weren't reporting any temp objects because it was
deemed unnecessary; but as it turns out, it is necessary if we want
to keep close track of DDL command execution inside one session.
Temp objects are reported as living in schema pg_temp, which works
because such a schema-qualification always refers to the temp
objects of the current session.
http://git.postgresql.org/pg/commitdiff/e9a077cad3799b41e8deef6fd8cb87e50164a791
- Remove variable shadowing. Commit a2e35b53 should have removed the
variable declaration in the inner block, but didn't. As a result,
the returned address might end up not being what was intended.
http://git.postgresql.org/pg/commitdiff/4e17e32f53c2de4a862ee5ef8bdcfa9152c11e25
- Fix autovacuum launcher shutdown sequence. It was previously
possible to have the launcher re-execute its main loop before
shutting down if some other signal was received or an error occurred
after getting SIGTERM, as reported by Qingqing Zhou. While
investigating, Tom Lane further noticed that if autovacuum had been
disabled in the config file, it would misbehave by trying to start a
new worker instead of bailing out immediately -- it would consider
itself as invoked in emergency mode. Fix both problems by checking
the shutdown flag in a few more places. These problems have existed
since autovacuum was introduced, so backpatch all the way back.
http://git.postgresql.org/pg/commitdiff/5df64f298d2863c9fb39437abb3ae6f988aedc0a
- Change SQLSTATE for event triggers
