Latest postgres app version5/5/2023 ![]() ![]() If you're self-hosting, upgrading between major PostgreSQL is easily done with pg_upgrade utility or a set of recommended practices in the official docs.Generally, you'd rather find a bug in an old version than in a new one.īefore choosing to upgrade, don't forget to check the list of rare cases that need manual actions before or after the upgrade. Upgrading is safe thanks to the half-year stabilization period between April's code freeze of every new feature and October's stable release. So, the TL DR: yes, you should update to improve stability. While some bug fixes are applied to previous versions, these changes require modifications to the ABI, interface functions, and system catalog structures, often not possible in an already-released major version. Bug fixes aren't as prominent as new features or performance improvements, but they often have a greater impact. The main reason to switch to a new PostgreSQL version is the large number of bug fixes that each new version delivers. You can find a full changelog and full list of new features in the official changelog. There are several new regular expressions functions that you may find useful for strings processing i.e. When you make a database backup with the provided pg basebackup extension you can also choose _Zstandard or ZL4 to compress database backups on the server side, to transfer less data over the network. WAL compression is useful to decrease disk space usage while safeguarding data integrity. In version 15 Zstandard and ZL4 can be chosen instead of pglz as a WAL compression method. Output log data as JSON structure helps logs processing and structured output on the client's side. In version 15 SELECT DISTINCT queries that drop duplicate rows from output can improve performance by using parallel workers. Parallel execution of queries using several worker processes is another part of PostgreSQL that develops fast. replicated data violate some constraint or there is a permission violation on a subscriber server user can choose to skip the conflicting transaction or disable the subscription until the user can decide how to handle the conflict. Also now you can choose parts of table data to logically replicate using i.e. Since version 15 two-phase commits are supported in logical replication. Logical replication is one of the fast-developing parts of PostgreSQL. For details on MERGE uses see: New features for logical replication Essentially merge can work as conditional delete/insert/update and also this makes PostgreSQL syntax implementation closer to SQL:2008 standard. This allows data processing without writing procedural language functions or complex CTE queries. The MERGE operation was introducedĪ new MERGE operation is to modify target table data according to the provided source with many available conditional processing options. Window functions performance is also improved. So increasing speed up to 4 times of both in-memory and on-disk sorts in version 15 is one of the main reasons to upgrade. Furthermore, sorting is one of the most algorithmically expensive operations. It is used not only when you use the ORDER BY clause, but also in indices creation, table partitioning, etc. Sorting rows of data is a frequent operation inside the PostgreSQL code. With this, you should not worry that a user that doesn't have access to a table could see its data through a view. WITH (security_invoker=on) to create a view that uses permissions of a view caller rather than a view creator to access underlying tables. And for the migrated database don't forget to revoke CREATE permission on the public schema manually to fit the new policy. It makes permission assigning more tunable ( details). ![]() The permission model is more secureĬREATE permission is revoked from all users except the database owner. The PostgreSQL community released version 15 (stable) in October 2022. ![]()
0 Comments
Leave a Reply. |