Considering breaking changes in PostgreSQL 17
PostgreSQL tries to keep the user interface as constant as possible. However, once in a while, breaking changes are necessary. This is, of course, also true for the current release.
Let us take a look at some of those changes. The first thing that has happened is the fact that support for AIX has dropped. This somehow makes sense because nobody here at CYBERTEC nor any other fellow PostgreSQL consultant I know has seen deployment on AIX in years.
The next thing is that --disable-thread-safety and MSVC builds have been dropped. All those things won’t hurt users at all.
What is more important is that some toolings have been removed from the contrib section. The one module I am referring to is adminpack, which has not been widely used anyway. The same is true for snapshot too old, which has been replaced with a way better implementation (transaction_timeout).
Finally, search_path is now fully secured during maintenance operations, which means that maintenance scripts should use fully qualified object names.
