{"id":103298,"date":"2022-02-11T15:36:48","date_gmt":"2022-02-11T13:36:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/obnovlenie-postgresql-vypusk-reshape-utility-dlya-migraczii-na-novuyu-shemu-bez-ostanovki-raboty"},"modified":"2022-02-11T15:36:48","modified_gmt":"2022-02-11T13:36:48","slug":"obnovlenie-postgresql-vypusk-reshape-utility-dlya-migraczii-na-novuyu-shemu-bez-ostanovki-raboty","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/obnovlenie-postgresql-vypusk-reshape-utility-dlya-migraczii-na-novuyu-shemu-bez-ostanovki-raboty","title":{"rendered":"PostgreSQL Update. Release reshape, a utility for migrating to a new schema without downtime.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Correction updates have been released for all supported PostgreSQL branches: 14.2, 13.6, 12.10, 11.15, and 10.20, fixing 55 issues discovered over the past three months. This includes resolving problems that, in rare circumstances, could lead to index corruption when modifying HOT (heap-only tuple) chains during the VACUUM operation or when performing REINDEX CONCURRENTLY on indexes for tables using the TOAST storage mechanism. <\/p>\n
Fixed the crashes during the execution of ALTER STATISTICS and while retrieving data with multirange types. Resolved errors in the query planner that led to incorrect results. Addressed memory leaks when updating indexes based on expressions and when performing the REASSIGN OWNED BY operation on a large number of objects. Enabled advanced statistics generation for partitioned tables. <\/p>\n
Additionally, the release of the reshape utility allows for complex updates to the data schema in PostgreSQL without stopping operations, which would normally require manual changes and downtime for services using the database. The utility enables a transition from the old data schema to the new one without prolonged locks, maintaining the request processing cycle. It automatically creates table views, allowing applications to continue operating during the data schema migration, and sets up triggers to relay data addition and removal operations between the old and new schemas. <\/p>\n
Thus, by using reshape during migration, the old and new schemas remain accessible simultaneously, allowing applications to be gradually transitioned to the new schema without downtime (in large infrastructures, handlers can be replaced step by step from old to new). After successfully migrating applications to the new schema, the views and triggers created to support the old schema are deleted. In case any application issues arise during migration, the schema change can be reverted, restoring the previous state. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"