These are the database, cloud, developer, and security news bits for the week ending August 18th brought to you by Compose. In this edition:
- PostgreSQL 11 - a look forward at what could come
- Better output paging for PostgreSQL now
- A RabbitMQ update hops up
- An update for the DB that makes PostgreSQL a TimescaleDB
- Using SQLite with the Z-shell
- Java EE is looking for a new home
- Twitter is making a fast Scala
- Microsoft ship .NET Core 2.0
- And finally, the future of HTTP Status code 418 in the balance.
Here are the NewsBits:
PostgreSQL - While PostgreSQL 10 is going through its beta process, Robert Haas has been surveying the development work being done for partitioning in PostgreSQL 11. Table partitioning is a big feature for the new PostgreSQL and is continually getting better. Amongst the plans, improvements to the foundations of the table partitioning, better output and explain, execution-time pruning, the ability to move rows between partitions, hash partitioning, default partitions that take rows that don't fit in other partitions and indexes that cover the whole partition table.
Paging PostgreSQL - Back to more practical matters with the release of pspg, the Psql Pager. This is an alternative to using
less to page results when using
psql. It features scrollable and freezable columns and selectable color schemes. You'll currently have to build from source but if you spend time peering at PostgreSQL output, it could well be worth it.
RabbitMQ - There's an update to RabbitMQ, 3.6.11 which now supports the Erlang OTP/20 update released a while back. Specifically, it apparently fixes a memory consumption under-report. (And if you're following, there was another milestone release of 3.7.0 as it works through its backlog).
TimescaleDB - TimescaleDB is actually PostgreSQL optimized for timescale data by way of an extension. We missed mentioning its update to 0.3.0 at the end if July. Brought to market by Timescale, its another good example of the great foundation that PostgreSQL offers to various database designs.
SQLite - SQLite gets everywhere, and the latest place you can find it is managing Zsh History. The zsh-histdb package does just that, building session and host tagged SQLite databases of Zsh history which can be merged together between hosts to create complete histories of your shell activity. It's interesting to observe how a simple thing like history can be made more observable using a database.
Java EE - Oracle has announced that it's looking to send Java EE to the Foundation Farm. Java EE 8 was, to say the least, a fractious drag through standards processes. Oracle thinks the entire thing would work better at another venue such as a foundation; it has worked with Apache and Eclipse in the past to re-home projects and says that in this case it would continue working in the new venue with Java EE interested parties.
Scala - Announced, but with no code yet, is Twitter's new Reasonable Scala. Twitter's focus for this Scala compiler is one thing: "dramatically" faster compilation. That includes going as far as looking at the overheads of Scala features with an eye to creating a Scala subset that compiles quickly. The end goal? To share that information with other Scala compiler builders. Twitter's a big Scala user and they say "compilation time is consistently among the top asks from our engineers."
.NET - Microsoft has shipped the final version of .NET Core 2.0, the open source apps platform that officially runs on Windows, Mac, and Linux. There's also a new Visual Studio 15.3 to go with it.
There is a request to the IETF to officially reserve the HTTP status code 418. The 418 code came about from a 1998 April Fools RFC which discussed a coffee pot control protocol.
The 418 status as meant to be returned by devices which were not capable of making coffee and translated to "I'm a teapot". It's since been quietly adopted as an easter egg and supported in some languages. But attempts to remove that support have kindled the Save 418 Movement to save the near 20-year-old whimsy.
If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at firstname.lastname@example.org. We're happy to hear from you.