The following feature has landed in Postgres 10 to help system administrators:

Password are hashed by default in PostgreSQL using MD5, more and more voices show up to mention that this is bad, particularly because it is possible to log into a server by just knowing the contents of pg_authid or find out about those hashes in past backups still lying around. Normally this data cannot be reached except by superusers, but things leaking sometimes, using MD5 can prove to be insecure in some cases (even if MD5 is strong against pre-image attacks for example). Postgres 10 is adding a new authentication protocol with the following commit:

Here is a feature for Postgres 10 that a couple of people will find useful regarding the handling of password files:

Last week the following commit has landed in Postgres 10 code tree, something that many users of servers with complicated connection policies will find useful:

One of my personal areas of work lately is in finding ways to improve the user experience with WAL archiving and pg_receivexlog. A couple of experiments have been done, and one of them has finished as a patch for upstream Postgres, in the shape of this commit:

Here are some news from the front of Postgres 10 development, with the highlight of the following commit:

Today’s post, the first one of 2017, is about the following feature of the upcoming Postgres 10:

It is too late for stories about Christmas, so here is a Postgres story about the following commit of Postgres 10:

Postgres 10 has support for an additional feature related to replication slots, a facility holding a way to retain WAL data in pg_xlog depending on the data consumed by clients connected to it. The feature spoken about here has been implemented by the following commit:

libpq is getting some improvements in its connection strings to define some properties that are expected from the backend server thanks to the following commit, that will be part of Postgres 10: