== PostgreSQL Weekly News - March 15 2015 ==
== PostgreSQL Product News ==
cstore_fdw 1.2, a columnar store extension for PostgreSQL, released
https://www.citusdata.com/blog/14-marco/120-cstore-fdw-1-2-release-notes
PG Partition Manager 1.8.2, an extension to manage time- or
serial-based table partitioning, released.
https://github.com/keithf4/pg_partman
pg_repack 1.3.1, a utility for removing bloat and restoring the
physical ordering of clustered indexes on line, released.
http://reorg.github.com/pg_repack/
pitrery 1.8, a set of bash scripts to manage PITR backups for
PostgreSQL, released.
http://dalibo.github.io/pitrery/
PostgreDAC 3.0.0 a Delphi/C++ builder for PostgreSQL, released.
http://microolap.com/products/connectivity/postgresdac/download/
== PostgreSQL Jobs for March ==
http://archives.postgresql.org/pgsql-jobs/2015-03/threads.php
== PostgreSQL Local ==
PGConf US 2015 takes place March 25-27, 2015 in NYC.
http://nyc.pgconf.us/2015/
The CfP for the second Swiss Postgres Conference, to be held June
25-26, 2015 at HSR Rapperswil, is open until April 1.
http://www.postgres-conference.ch/cfp/
The constituent assembly of the Swiss PostgreSQL
Users Group (SwissPUG) will be Friday, April 10, 2015
http://www.swisspug.org
India PostgreSQL UserGroup will hold a PGday in Bengaluru, Karnataka,
India on April 11, 2015. RSVP at
http://www.meetup.com/India-PUG/events/220553997/
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/
PGCon 2015 is June 16-20 in Ottawa, Canada.
http://www.pgcon.org/2015/
== 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:
- Add missing "goto err" statements in xlogreader.c. Spotted by
Andres Freund.
http://git.postgresql.org/pg/commitdiff/c74c04b8aa03f05983f940ee94c86a5cc1945393
- Fix typo in comment.
http://git.postgresql.org/pg/commitdiff/828599acecdb2929f9b66d6f590c2abbc751b58b
- Suppress maybe-uninitialized compiler warnings. Previously some
compilers were thinking that the variables that 57aa5b2 added
maybe-uninitialized. Spotted by Andres Freund
http://git.postgresql.org/pg/commitdiff/cd6c45cbeec5e21b470e9a8d19e02f60f1a52807
- Add GUC to enable compression of full page images stored in WAL.
When newly-added GUC parameter, wal_compression, is on, the
PostgreSQL server compresses a full page image written to WAL when
full_page_writes is on or during a base backup. A compressed page
image will be decompressed during WAL replay. Turning this parameter
on can reduce the WAL volume without increasing the risk of
unrecoverable data corruption, but at the cost of some extra CPU
spent on the compression during WAL logging and on the decompression
during WAL replay. This commit changes the WAL format (so bumping
WAL version number) so that the one-byte flag indicating whether a
full page image is compressed or not is included in its header
information. This means that the commit increases the WAL volume
one-byte per a full page image even if WAL compression is not used
at all. We can save that one-byte by borrowing one-bit from the
existing field like hole_offset in the header and using it as the
flag, for example. But which would reduce the code readability and
the extensibility of the feature. Per discussion, it's not worth
paying those prices to save only one-byte, so we decided to add the
one-byte flag to the header. This commit doesn't introduce any new
compression algorithm like lz4. Currently a full page image is
compressed using the existing PGLZ algorithm. Per discussion, we
decided to use it at least in the first version of the feature
because there were no performance reports showing that its
compression ratio is unacceptably lower than that of other
algorithm. Of course, in the future, it's worth considering the
support of other compression algorithm for the better compression.
Rahila Syed and Michael Paquier, reviewed in various versions by
myself, Andres Freund, Robert Haas, Abhijit Menon-Sen and many
others.
http://git.postgresql.org/pg/commitdiff/57aa5b2bb11a4dbfdfc0f92370e0742ae5aa367b
Michael Meskes pushed:
- Ignore object files generated by ecpg test suite on Windows. Patch
by Michael Paquier
http://git.postgresql.org/pg/commitdiff/b9e538b190d9cf4387361214eadc430393ebf852
- Ignore leftover artifacts from ecpg testsuite runs on Windows.
http://git.postgresql.org/pg/commitdiff/fa83f809458a966dff225d3d266399d48e7b5e6e
- Revert
