== PostgreSQL Weekly News - September 13 2015 ==
== PostgreSQL Product News ==
pgbouncer 1.6.1, a light-weight connection pooler for PostgreSQL,
released. This is a security upgrade.
https://pgbouncer.github.io/2015/09/pgbouncer-1-6-1/
== PostgreSQL Jobs for September ==
http://archives.postgresql.org/pgsql-jobs/2015-09/
== PostgreSQL Local ==
PostgresOpen 2015 will being held in Dallas, Texas September 16-18.
http://2015.postgresopen.org/
PostgreSQL Session #7, will be held September 24th, 2015 in Paris,
France,
http://www.postgresql-sessions.org/7/about
PGDay.IT 2015 will take place in Prato on October 23, 2015.
http://pgday.it
PostgreSQL Conference Europe 2015 will be held on October 27-30 in the
Vienna Marriott Hotel, in Vienna, Austria. The schedule is posted.
http://2015.pgconf.eu/
PGConf Silicon Valley 2015 is November 17-18 at the South San
Francisco Convention Center.
http://www.pgconfsv.com
PgCUBA will take place October 19-23, 2015 in Havana. Spanish
language information below:
http://www.postgresql.org/about/event/1813/
PGBR2015 (The Brazilian PostgreSQL Conference) will take place in Porto
Alegre, Rio Grande do Sul, on November 18, 19 and 20. The CfP is open
until August 31.
http://pgbr.postgresql.org.br/2015/en/#call-for-papers
PGConf.DE will be held on November 26-27, 2015 in Hamburg, Germany, at
the Lindner Hotel am Michel.
http://2015.pgconf.de/
== 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 ==
Teodor Sigaev pushed:
- Update site address of Snowball project
http://git.postgresql.org/pg/commitdiff/a1c44e1af62f7247610ee80bb355ef7084c24001
- Add pages deleted from pending list to FSM. Add pages deleted from
GIN's pending list during cleanup to free space map immediately.
Clean up process could be initiated by ordinary insert but adding
page to FSM might occur only at vacuum. On some workload like
never-vacuumed insert-only tables it could cause a huge bloat. Jeff
Janes.
http://git.postgresql.org/pg/commitdiff/e95680832854cf300e64c10de9cc2f586df558e8
- Make GIN's cleanup pending list process interruptable. Cleanup
process could be called by ordinary insert/update and could take a
lot of time. Add vacuum_delay_point() to make this process
interruptable. Under vacuum this call will also throttle a vacuum
process to decrease system load, called from insert/update it will
not throttle, and that reduces a latency. Backpatch for all
supported branches. Jeff Janes.
http://git.postgresql.org/pg/commitdiff/e26692248ada18417199b47bc2e4e1648d530953
- Microvacuum for GIST. Mark index tuple as dead if it's pointed by
kill_prior_tuple during ordinary (search) scan and remove it during
insert process if there is no enough space for new tuple to insert.
This improves select performance because index will not return tuple
marked as dead and improves insert performance because it reduces
number of page split. Anastasia Lubennikova
with minor editorialization by me
http://git.postgresql.org/pg/commitdiff/013ebc0a7b7ea9c1b1ab7a3d4dd75ea121ea8ba7
- Fix oversight in 013ebc0a7b7ea9c1b1ab7a3d4dd75ea121ea8ba7 commit.
Declaration of variable inside code block.
http://git.postgresql.org/pg/commitdiff/223936e22691ccae02be7e2980b6f565518bff19
Gregory Stark pushed:
- Change type of DOW/DOY to UNITS
http://git.postgresql.org/pg/commitdiff/37239ef8c9fa72e0f73a307cc413a03a743878d3
Jeff Davis pushed:
- Add log_line_prefix option 'n' for Unix epoch. Prints time as Unix
epoch with milliseconds. Tomas Vondra, reviewed by Fabien Coelho.
http://git.postgresql.org/pg/commitdiff/f828654e1097bdbb40fedebd9ac1ea045b183e15
- Coordinate log_line_prefix options 'm' and 'n' to share a timeval.
Commit f828654e introduced the 'n' option, but it invoked
gettimeofday() independently of the 'm' option. If both options were
in use (or multiple 'n' options), or if 'n' was in use along with
csvlog, then the reported times could be different for the same log
message. To fix, initialize a global variable with gettimeofday()
once per log message, and use that for both formats. Don't bother
coordinating the time for the 't' option, which has much lower
resolution. Per complaint by Alvaro Herrera.
http://git.postgresql.org/pg/commitdiff/b1e1862a123b6904d51fd0a607e30f5832bf9a1f
Álvaro Herrera pushed:
- Add more sanity checks in contrib/sslinfo. We were missing a few
return checks on OpenSSL calls. Should be pretty harmless, since we
haven't seen any user reports about problems, and this is not a
high-traffic module anyway; still, a bug is a bug, so