2015-02-26 07:11:15 +0000
Up to Postgres 9.4, when a node in recovery checks for the availability of WAL from a source, be it a WAL stream, WAL archive or local pg_xlog and that it fails to obtain what it wanted, it has to wait for a mount of 5s, amount of time hardcoded directly in xlog.c. 9.5 brings more flexibility with a built-in parameter allowing to control this interval of time thanks to this commit:
Read more...2015-02-20 13:35:23 +0000
Not later than this week a bug regarding [pg_dump] (https://www.postgresql.org/docs/devel/static/app-pgdump.html) and compression with zlib when dumping data has been reported [here] (https://www.postgresql.org/message-id/20150217153446.2590.24945@wrigleys.postgresql.org).
Read more...2015-02-13 06:27:13 +0000
As a preparation of an upcoming patch for full-page write compression in WAL, a patch has been pushed this week to make PGLZ, the in-core compression algorithm of PostgreSQL used for TOAST tables, more pluggable for plugins and frontend applications, particularly pg_xlogdump that needs to be able to decode a WAL record using the XLOG reader facility even if blocks are compressed to be able to reconstitute them. It makes as well sense to expose this algorithm as PGLZ compressed data would not be limited only to the internal backend usage of TOAST tables in a PostgreSQL instance, but as well to WAL data, be it simple WAL archive or a WAL streaming flow. So, here is the commit:
Read more...2015-02-01 12:20:22 +0000
A couple of days ago the following commit has popped up in PostgreSQL tree for the upcoming 9.5, introducing a feature particularly interesting for developers of backend extensions and plugins:
Read more...2015-01-27 02:05:34 +0000
A couple of days back a new mode has been added in [vacuumdb] (https://www.postgresql.org/docs/devel/static/app-vacuumdb.html) for the support of parallel jobs:
Read more...Unless otherwise specified, the contents of this website are (C)Copyright Michael Paquier 2010-2025 and are licensed for use under CC BY-NC-ND 4.0.