{"id":33294,"date":"2024-05-27T08:05:58","date_gmt":"2024-05-27T06:05:58","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=33294"},"modified":"2024-05-27T08:09:31","modified_gmt":"2024-05-27T06:09:31","slug":"time-to-test-postgresql-17beta1-is-there","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/time-to-test-postgresql-17beta1-is-there\/","title":{"rendered":"Time to test: PostgreSQL 17beta1 is there"},"content":{"rendered":"\n

It is this time of the year when a new PostgreSQL major version beta release is available for testing. PostgreSQL 17 (scheduled to be released later this year) is no exception to that: Last week, the first beta of PostgreSQL 17 was announced<\/a>. While many people are not really interested in beta releases, they really should be, especially when it comes to critical applications. If they \/ you test now, potential bugs can be fixed before the final version will be released.<\/p>\n\n\n\n

I am absolutely aware that testing takes time, but this time is spend wisely and you can really help the PostgreSQL community be reporting back any issues you’ll face. The earlier you can do this, the better.<\/p>\n\n\n\n

The release announcement<\/a> contains a summary of the major new features you might be interested in. But there is much more to explore in the release notes<\/a> (just keep in mind that the release notes are also subject to change until the final release of PostgreSQL 17).<\/p>\n\n\n\n

I’ve written about some of the new features here on this blog and if you want to follow up here is the list of blog posts:<\/p>\n\n\n\n