{"id":184329,"date":"2026-11-20T03:36:27","date_gmt":"2026-11-20T01:36:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/reliz-subd-postgresql-19"},"modified":"2026-11-20T03:36:30","modified_gmt":"2026-11-20T01:36:30","slug":"postgresql-19-released","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/postgresql-19-released","title":{"rendered":"Release of the PostgreSQL 19 DBMS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>After a year of development, a new stable branch of the PostgreSQL DBMS, version 19, has been released. Updates for this new branch will be released over the next five years until November 2031. Support for PostgreSQL 14.x, the oldest supported branch, ends this month. The release was published almost two months later than originally planned due to an atypically high number of error reports identified through code analysis using AI tools.       <\/p>\n<p>Key innovations:     <\/p>\n<ul>\n<li class=\"l\"> The implementation of the asynchronous I\/O subsystem has been enhanced, allowing for increased input\/output throughput and the elimination of delays. In the universal AIO implementation (io_method=worker), the capability for automatic scaling of the number of running I\/O handler processes based on load has been introduced. Parameters such as io_min_workers, io_max_workers, io_worker_idle_timeout, and io_worker_launch_interval have been proposed to define the minimum and maximum number of handler processes as well as the inactivity timeout before termination and the delay before launching processes.\n<p>In addition, the prefetching scheduler used in AIO is optimized to enhance performance for queries that require loading large amounts of data from disk. The optimization is achieved through adaptive determination of the allowable number of prefetch operations based on the nature and size of the request (for example, for operations scanning large tables and indexes, more data is now preloaded from disk in advance). To analyze the performance of input\/output operations in asynchronous mode, the option 'IO' has been added to the 'EXPLAIN ANALYZE' command.      <\/p>\n<li class=\"l\"> The pg_plan_advice and pg_stash_advice extensions have been added to pass plan hints to the query planner in a mini-language called 'plan advice', enabling influence over the choice of execution plans, fixing selected plans, and experimenting with different plans. To retrieve a list of parameters chosen by the planner when executing a query, the 'PLAN_ADVICE' option has been added to the EXPLAIN command, and to set your own parameters before executing a query, you can use the expression 'SET pg_plan_advice.advice = \u2018string with parameter list\u2019.' The pg_stash_advice extension complements pg_plan_advice with the capability to bind parameters to query identifiers to avoid adding them before each query. EXPLAIN (COSTS OFF, PLAN_ADVICE) SELECT * FROM join_fact f JOIN join_dim d ON f.dim_id = d.id; \u2026 Generated Plan Advice: JOIN_ORDER(f d) HASH_JOIN(d) SEQ_SCAN(f d) NO_GATHER(f d) SET pg_plan_advice.advice = \u2018JOIN_ORDER(f d) NO_GATHER(f d)\u2019;\n<li class=\"l\"> The autovacuum process has been enhanced to allow for the parallel use of multiple workers when cleaning indexes. The number of workers can be configured through the autovacuum_max_parallel_workers option. Additionally, new options have been introduced: autovacuum_vacuum_score_weight, autovacuum_vacuum_insert_score_weight, and autovacuum_analyze_score_weight to determine the priority of table cleaning.\n<li class=\"l\"> A new cleaning strategy has been implemented, which reduces the workload in the future by updating the visibility map during table scans while executing SELECT queries, without waiting for the VACUUM command to run.\n<li class=\"l\"> A new SQL command 'REPACK' has been added to rebuild tables with lower overhead. The REPACK command completely rewrites all the contents of a table into a new file on disk, allowing the operating system to reclaim disk space occupied by unused blocks. Unlike the 'VACUUM FULL' command, which enforces a hard lock during the rewrite, the REPACK command has a 'CONCURRENTLY' option that allows other transactions to use the table during repacking. Unlike the pg_repack extension, REPACK is noticeably faster as it does not attach additional triggers to the table but does not support processing entirely partitioned tables.\n<li class=\"l\"> Performance of the INSERT operation has been increased by up to two times for tables where records are checked against foreign keys (Foreign Key). This acceleration has been achieved by leveraging the index for foreign key checks, which eliminates the need for a resource-intensive internal query to the table.\n<li class=\"l\"> The query planner now recognizes Anti-Join operations (identifying rows in the first table that have no matches in the second table) in complex queries with LEFT JOIN and queries with NOT IN expressions to leverage specific optimizations. The application of incremental sorting has been expanded. An 'eager aggregation' optimization has been added, moving aggregation operations to a stage before table merging to reduce the number of rows processed during the merge. Parallel execution of sequential scan operations has been accelerated. The constructs 'IS DISTINCT FROM' and 'IS NOT DISTINCT FROM' have been simplified to expressions using the operators '' and '=', provided that both operands cannot take the value NULL.\n<li class=\"l\"> The efficiency of delivering notifications using the NOTIFY command in multi-channel notification configurations has been improved. A channel map is now stored in shared memory, allowing direct addressing only to backends subscribed to a given channel.\n<li class=\"l\"> The INSERT command has been enhanced with support for the ON CONFLICT DO SELECT ... RETURNING expression, which returns records if they cannot be added via INSERT, in addition to the ON CONFLICT DO NOTHING\/UPDATE expressions that silently ignore conflicts during insertion or update instead of inserting.\n<li class=\"l\"> Support for outputting data in JSON format has been added to the COPY command.\n<li class=\"l\"> String processing methods lower(), upper(), replace(), split_part(), and btrim() have been added to the SQL\/JSON language.\n<li class=\"l\"> Window functions lead(), lag(), first_value(), last_value(), and nth_value() have been updated to support the 'IGNORE NULLS' expression for skipping NULL values.\n<li class=\"l\"> A 'WAIT FOR LSN' command has been added, which, during asynchronous replication, allows pausing a SELECT query on the replicated server until changes from the primary server are applied to prevent outdated data from being output. <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/en\/server\/dts-los-angeles\/\"   title=\"server\" data-wpil-keyword-link=\"linked\">server<\/a>.\n<li class=\"l\"> The random() function now supports date and timestamp types for generating random dates and times within a specified range.\n<li class=\"l\"> It is now possible to create functions in PL\/Python for event triggers.\n<li class=\"l\"> Support for the TLS SNI (Server Name Indication) extension has been added for using TLS certificates bound to hostnames that the client accesses when establishing an encrypted connection over a single IP address. <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/en\/server\/\"   title=\"server\" data-wpil-keyword-link=\"linked\">server<\/a> The parameter password_expiration_warning_threshold has been added to the postgresql.conf configuration file, which allows for the setup of a warning output for the impending expiration of a password.\n<li class=\"l\"> Warning outputs are now enabled by default when using the MD5 authentication algorithm, which has been deprecated. To disable such warnings, the parameter md5_password_warnings has been added.\n<li class=\"l\"> New views have been added: 'pg_stat_lock' to view accumulated statistics on locks by lock type; 'pg_stat_recovery' to obtain information on the state of recovery operations; 'pg_stat_autovacuum_scores' to determine the priority of table processing in autovacuum. Many system views now include a 'stats_reset' column, which reflects the last time the counters were reset. The 'pg_stat_progress_vacuum' and 'pg_stat_progress_analyze' views have been enhanced with a 'started_by' column that shows the initiator of the operation. In the pg_stat_progress_vacuum view, a 'mode' column has been added that reflects the applied cleanup mode.\n<li class=\"l\"> New views have been added: 'pg_stat_lock' for viewing accumulated statistics on locks concerning lock types; 'pg_stat_recovery' for obtaining information on the state of recovery operations; 'pg_stat_autovacuum_scores' for determining table processing priorities in autovacuum. Many system views have been enhanced with a 'stats_reset' column indicating the last time the counters were cleared. The 'pg_stat_progress_vacuum' and 'pg_stat_progress_analyze' views have been updated with a 'started_by' column showing the initiator of the operation. The 'pg_stat_progress_vacuum' view has also gained a 'mode' column indicating the cleaning mode applied.\n<li class=\"l\"> Information about the size of full pages written to the WAL log has been added to the statistics shown after VACUUM and ANALYZE operations, as well as to the 'pg_stat_wal' view. This simplifies the analysis of the reasons for excessive WAL log growth (making it possible to determine if the growth is related to the full_page_writes parameter).\n<li class=\"l\"> Statistics presented after VACUUM and ANALYZE operations, as well as in the view , include information about the size of full pages written to the WAL log, which simplifies the analysis of the reasons for excessive WAL log growth (it can determine whether the increase is related to the use of the full_page_writes parameter).\n<li class=\"l\"> The logical replication mechanism has been enhanced to support the replication of SEQUENCE values, which can be published using the CREATE PUBLICATION command with the expression FOR ALL SEQUENCES.\n<li class=\"l\"> The syntax CREATE PUBLICATION \u2026 EXCEPT has been added for replicating all tables except for those explicitly specified.\n<li class=\"l\"> The CREATE SUBSCRIPTION \u2026 SERVER expression has been added, allowing the creation of logical replication subscriptions by obtaining connection settings from a remote server.\n<li class=\"l\"> It is now possible to enable logical replication on the fly without restarting the server, even if the wal_level parameter is set to replica instead of logical. To determine the actual logging level not tied to the wal_level setting in the configuration file, the effective_wal_level parameter has been added.\n<li class=\"l\"> In the Foreign Data Wrapper (postgres_fdw) external table connection mechanism, capabilities have been implemented to pass array operations to a remote server, and the option import_stats has been added for importing statistics for tables from an external server when executing the ANALYZE command to enhance local query execution planning efficiency.\n<li class=\"l\"> JIT compilation is disabled by default, as it provides a noticeable performance gain mainly for heavy analytical queries, while for regular OLTP workloads, it may lead to performance drops due to mispredictions of the resources needed to execute the queries.\n<li class=\"l\">  To improve the performance of compression and decompression of TOAST tables, the default_toast_compression parameter has been set to lz4.\n<li class=\"l\"> Support for authentication using the RADIUS protocol has been removed.\n<li class=\"l\"> In the vacuumdb \u2014analyze-only command, analysis of partitioned tables is enabled by default.<\/ul>\n<p>Due to issues identified in the final testing phase, some features presented in the beta version, such as the GROUP BY ALL syntax, support for non-text output formats in pg_dumpall, SQL\/PGQ for graph queries, on-the-fly inclusion of checksum support without reboot and reinitialization, the FOR PORTION OF expression in UPDATE and DELETE, the ALTER TABLE \u2026 MERGE PARTITIONS and ALTER TABLE \u2026 SPLIT PARTITIONS expressions for reorganizing partitioned tables, and setting LC_COLLATE to C for the postmaster process, along with new functions pg_get_role_ddl(), pg_get_tablespace_ddl(), and pg_get_database_ddl(), were not included in the release. This news is sponsored by Hi-Square, the developer of the Low-Code platform XSQUARE based on PostgreSQL (advertisement, LLC \u2018Hi-Square\u2019, INN 7718990614).<br \/>\n<br \/>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=66693\">opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430. \u041f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0430 PostgreSQL 14.x, \u0441\u0430\u043c\u043e\u0439 \u0441\u0442\u0430\u0440\u043e\u0439 \u0438\u0437 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u043c\u044b\u0445 \u0432\u0435\u0442\u043e\u043a, \u043f\u0440\u0435\u043a\u0440\u0430\u0449\u0435\u043d\u0430 \u0432 \u044d\u0442\u043e\u043c \u043c\u0435\u0441\u044f\u0446\u0435. \u0420\u0435\u043b\u0438\u0437 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d \u043f\u043e\u0447\u0442\u0438 \u043d\u0430 \u0434\u0432\u0430 \u043c\u0435\u0441\u044f\u0446\u0430 \u043f\u043e\u0437\u0434\u043d\u0435\u0435 \u0438\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e \u043d\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u043e\u0439 \u0434\u0430\u0442\u044b \u0438\u0437-\u0437\u0430 \u043d\u0435\u0441\u0432\u043e\u0439\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0448\u043b\u044b\u043c \u0432\u044b\u043f\u0443\u0441\u043a\u0430\u043c \u043f\u043e\u0442\u043e\u043a\u0430 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u043e\u0448\u0438\u0431\u043a\u0430\u0445, \u0432\u044b\u044f\u0432\u043b\u0435\u043d\u043d\u044b\u0445 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-184329","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Alexander Kovalev\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/news\/postgresql-19-released\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 \u0421\u0423\u0411\u0414 PostgreSQL 19 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/news\/postgresql-19-released\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-11-20T01:36:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-20T01:36:30+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Release of DBMS PostgreSQL 19 | ProHoster","description":"After a year of development, a new stable branch of the PostgreSQL DBMS version 19 has been released. Updates for the new branch will be provided for five years until November 2031.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/news\/postgresql-19-released","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 \u0421\u0423\u0411\u0414 PostgreSQL 19 | ProHoster","og:description":"\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430.","og:url":"https:\/\/prohoster.info\/en\/blog\/news\/postgresql-19-released","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2026-11-20T01:36:27+00:00","article:modified_time":"2026-11-20T01:36:30+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":[],"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/184329","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=184329"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/184329\/revisions"}],"predecessor-version":[{"id":184330,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/184329\/revisions\/184330"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=184329"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=184329"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=184329"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}