RSS
Логотип
Баннер в шапке 1
Баннер в шапке 2

Postgres Pro Shardman

Product
The name of the base system (platform): PostgreSQL DBMS
Developers: Postgres Professional (PPG, Postgres Professional)
Date of the premiere of the system: 2024/03/04
Last Release Date: 2025/12/01
Technology: DBMS

Content

Main article: Database Management System (DMS)

2025

Silk extension: support for Select, Update, Delete and prepared statements

Postgres Professional on December 1, 2025 announced the release of an updated version of Postgres Pro Shardman, an industrial DBMS for managing distributed databases and building highly scalable clusters. This release includes both enhanced functionality and significant improvements in performance and reliability.

The update is focused on organizations that need horizontal scaling, a single point of administration and stable operation of a distributed PostgreSQL cluster under high loads.

Key technological improvements:

1. Faster Queries Inside the Shards - Optimizing Local Access
The release introduced optimization that chooses the fastest way to execute queries when the data is in one section. This reduces latency and reduces network load, speeding up the operation of "heavy" operations on clusters with a large number of segments.

2. Significant Silk extension: support for SELECT, UPDATE, DELETE and prepared statements
Silk is a mechanism that allows operations to be pushed closer to data. Silk now supports not only SELECT, but also UPDATE/DELETE, as well as prepared statements. The result is less network traffic for crossshard requests, which allows you to perform complex distributed requests with lower costs.

3. Full support for Row-Level Security on global and segmented tables
Now row-level security policies (RLS) work in all types of tables in a distributed cluster. This is critical for systems where data must be physically separated, but logically managed centrally - banks, telecom, government customers.

4. Improved control over transaction consistency and snapshots (READ COMMITTED + CSN)
Two READ COMMITTED modes have been added with or without CSN snapshot support. This helps to avoid dirty reads in distributed scenarios with intensive transactional load and more accurately manage query isolation.

5. Unified approach to password policies in a distributed cluster
Advanced password policies and global profiles are supported. It became possible to specify system users for which:

  • authorization events between nodes are not propagated,
  • blocking is prohibited,
  • Backup servers are allowed to run.

This facilitates the operation of a large cluster environment.

6. SSL for Silk
Silk now supports SSL. This improves the security of * distributed computing and reduces external traffic encryption requirements.

Administration management and improvement tools:

  • BiHA Secure Control Channel Mode

BiHA control channel can operate in a secure mode - an important requirement for customers working in isolated or regulated circuits.

  • Backup and Recovery Enhancements
    • Rolling-backup now correctly takes into account the state of leaders and reserves.
    • Fixed PANIC issue during rebalancing.
    • Updated schema and consistency validation mechanisms.

The release includes a number of key extensions that improve the security, stability and compatibility of Shardman with new PostgreSQL components.

File:Aquote1.png
Customers are not just waiting for technology - they are waiting for guaranteed stability and scale. Shardman closes this request, allowing you to build complex systems without the risk of data loss and with predictable performance. We consider this release as strengthening the entire Russian DBMS industry - noted CPO Postgres Professional Artyom Galonsky.
File:Aquote2.png

Distributed database Shardman: horizontal scaling for enterprise tasks based on Postgres Pro

For a business that strives for technological independence and works with ever-growing amounts of data, it is critical to be able to scale the databases used. This is a key part of the strategy.

The distributed Shardman DBMS, created as a result of Postgres Professional research conducted in 2017, allows you to horizontally distribute data without loss in consistency and manageability, while providing a single data array, as if your application uses one database. In the review, we will look in detail at when to implement charding, how Shardman copes with the limitations of traditional approaches, and why it became the choice for migrations from Oracle at volumes over 60 TB. Read more here.

Postgres Pro Shardman 17.5.1

Postgres Professional has released updates for Postgres Pro Shardman 17.5.1. The solution uses data charring to work efficiently with large amounts of information (up to a petabyte) and a high transaction load. The company announced this on August 7, 2025.

Improved management and fault tolerance

Postgres Pro Shardman includes the shardmanctl utility, which has received new features for managing the cluster:

  • Check of circuit integrity. The shardmanctl schema verify command checks the consistency of information about parties, tables, roles and other schema objects throughout the cluster.
  • Backup for BiHA. Added the ability to use pg_probackup as a backup method for high availability (BiHA) configurations.
  • Flexible recovery. The restore command now supports recovering only metadata or schema, as well as restoring individual shards.

The information capabilities of the crash_info module for problem diagnostics have been expanded.

Module Updates:

  • pg_proaudit - new object types and event fields (UUID, XID, VXID) have been added for a more accurate and complete audit;
  • pgpro_pwr 4.9 - improved collection of statistics on servers and schema objects, which gives DBA more tools for analysis;
  • pgpro_stats 1.9 - Extended session tracing to provide more detailed information about query execution.

2024: Versions 14.15.3 and 14.15.4

Postgres Professional has released an update to the Postgres Pro Shardman DBMS. The company announced this on February 21, 2025.

Versions 14.15.3 and 14.15.4 include the capabilities of the previous release of 14.15.2, as well as the release of the free DBMS PostgreSQL 14.15. Current versions of the DBMS have improved performance and fixed some bugs.

Among the key changes are:

A.1.1. Core and Extensions

  • Added a shardman.pg_indoubt_xacts view that displays transaction information in the InDoubt state.
  • Added global views for system catalog and statistics.
  • Added the ability to bring type conversion operations to the remote server.
  • A constraint has been added for segmented tables that can refer to themselves only if the foreign key references the same section of the segmented table.

Also, the etcd module has been updated to version 3.5.18.

A.1.2. Management utilities

  • A new show-config subcommittee has been added for the shardmanctl probackup command, which displays all the current pg_probackup configuration parameters, including those contained in the pg_probackup.conf file, as well as those specified on the command line.
  • Added options for sharmanctl probackup delete and shardmanctl probackup backup for working with backup retention policies: retention-redundancy, retention-window, wal-depth, delete-expired, merge-expired.
  • The supported version of the pg_probackup utility has been updated to 2.8.7.

2024

Versions 14.13.2 and 14.13.3

Postgres Professional has released an update to the Postgres Pro Shardman DBMS. Versions 14.13.2 and 14.13.3 have improved performance, added features, and fixed some bugs. The developer announced this on November 5, 2024.

Key changes to version 14.13.2 include:

Core and Extensions

  • Read event handling control now has switchable modes that can be set through shardman.silf-flow-control. Modes supported are none, round_robin, and shortest_job_first.
  • Added configuration parameters - a shardman.sync_cluster_settings that controls the synchronization of all configuration parameters set by the user in the cluster, as well as a shardman.sync_cluster_settings_blacklist that excludes parameters of the remote cluster that do not need to be synchronized.
  • Added enable_sql_func_custom_plans configuration option. Enabling this option allows you to create custom plans for SQL functions . By default, enabled for new clusters and disabled for old clusters.

Management utilities

  • The shardmanctl psql command has been added, which, without the specified default parameters, creates a connection to the first available main node. If --shard is specified, the connection occurs to the current main node of the segment.
  • Added lz4 compression method for default_toast_compression parameter.

For version 14.13.3:

Core and Extensions

  • Added configuration settings to manage the collection of server failure information. The crash_info option includes this functionality, and the crash_info_dump and crash_info_location specify the content and location of the fault files, respectively.
  • Management utilities
  • Fixed an error switching from the master server to the replica when the server configuration settings cannot be retrieved.

Postgres Pro Shardman 14.12.2

Postgres Professional has released an updated version of the Postgres Pro Shardman 14.12.2 DBMS. The developer announced this on August 8, 2024.

Postgres Pro Shardman is distributed relational DBMSs for high-load systems, suitable for the largest installations up to a hundred TB and above, when a single server is not enough. DBMS allows you to divide data into parts and distribute it to different servers - shards. At the same time, the solution provides built-in fault tolerance and guaranteed compliance with ACID requirements: atomicity, consistency, isolation and stability.

The current release adds some features, improves performance, and fixes some bugs. Among the most important changes:

Added the ability to create a global or segmented table based on another global, segmented, or local. As of August 2024, there are restrictions on creating tables based on local ones.

Fixed IF NOT EXISTS processing of CREATE TABLE command for global and partitioned tables. Previously, there was a possibility of creating a table with an incorrect structure if a partitioned table with an identical name already existed on one of the cluster nodes.

Updated the default value for the num_parts storage parameter by 24 to achieve a more uniform distribution of data for clusters with 2, 3, 4, 6, and 8 nodes. A enable_merge_append configuration option has been added that enables or disables the use of MergeAppend plans by the scheduler. In particular, it allows you to disable the use of these plans if they are too expensive.

A pgpro_stats.track_shardman_connections configuration parameter has been added that enables or disables the processing of Shardman statements.

Added the ability to make connections to the VALUES expression on the remote server. The 64 thousand limit on the number of tables in the query has been removed.

Added a shardman.pg_stat_monitor view that provides statistics on the distributed deadlock detector and prepared transaction resolution services.

Added a global shardman.gv_stats_sdm_statements view that provides access to aggregated statistics for distributed queries.

Updated view of pgpro_stats pgpro_stats_sdm_statements. Now it contains statistics only for queries that use segmented tables.

Updated the supported version of the pg_probackup utility to 2.8.2. Management utilities

Added the ability to back up a cluster with table spaces that are now in the backup directory.

Added the ability to restore a fully or partially working cluster from a backup made on a partially working cluster using shardmanctl probackup.

The --no-wait parameter was introduced for the shardmanctl shard add command, with which the shardmanctl command does not wait for the segment to start and unlocks other commands. The s|--scale parameter for the shardmanctl bench run command was entered. Specifies the scaling factor by which the number of rows generated is multiplied. The shardmanctl script command has been added, which executes non-transaction commands from a file or command line on the specified segments.

The sdmspec.json configuration file generated by the shardmanctl config generate command has been changed. The file excludes parameters that depend on system resources and workload on the cluster node. These settings retain the default values. Previously, cluster initialization may have failed on nodes with smaller resources due to high values of these parameters.

Added the ability to restore others from a backup of one cluster if they have the same topology. The command shardmanctl config update ip has been added, which updates the IP addresses of the specified cluster nodes.

The --log-format parameter has been added to shardmand, which specifies the format of the log: json or text.

Postgres Pro Shardman Minor Update Release Version 14.12.1

Postgres Professional on June 20, 2024 announced the release of minor updates to Postgres Pro Shardman version 14.12.1.

Postgres Pro Shardman is distributed relational DBMSs for high-load systems, suitable for the largest installations in tens and hundreds of TB, when a single server is not enough. DBMS allows you to divide data into parts and distribute it to different servers - shards. At the same time, the solution provides built-in fault tolerance and guaranteed compliance with ACID requirements: atomicity, consistency, isolation and stability.

In the next release, Postgres Pro Shardman has added various features, improved performance and fixed some bugs. Among the key changes are:

Core and Extensions

  • The REMOTE parameter of the EXPLAIN command has been added, which allows the EXPLAIN output for requests made on the remote server. By default, enabled.
  • Own logic for estimating the cost of plans is implemented. It allows the scheduler to more often choose common plans with the similarity of common and specialized.
  • Added support for partitioning during execution for plan nodes that aggregate data on third-party servers. First of all, optimization is necessary to eliminate sections in general plans.
  • Added cumulative metrics on the amount of network traffic between Shardman cluster nodes in the view shardman.pg_stat_netusage.
  • Updated the pg_stat_activity view, which now shows the status of Shardman service processes.

Management utilities

  • Fixed CVE-2023-45288 and CVE-2023-44487 vulnerabilities.
  • Fixed an error in the shardmanctl cleanup command that caused replication groups to not be deleted.
  • Improved output of the shardmanctl forall command when the result is empty.
  • Fixed a previous shardmand failure if the Shardman cluster is not fully configured.

Release of Shardman

Postgres Professional March 4, 2024 announced the release of Shardman - distributed DBMS for high-load systems. The DBMS was developed specifically at the request of customers and is suitable for the largest installations in tens and hundreds of TB, when a single one servers is not enough. Shardman is already listed in, certified and in the Register of Russian Software FSTEC final stages in testings large companies oil and gas financial and the sector.

From an architectural point of view, Shardman is a distributed DBMS consisting of several servers, where each shard stores part of the data. At the same time, some servers are used to replicate the data of each shard, which ensures fault tolerance. For communication between charms, a multiplexer is used - a special "transport," which optimizes work with the network and the load on the DBMS when performing distributed requests. Shardman is distinguished by three key features:

  • Scale horizontally. When the DBMS server ceases to cope with loads, the data stored on it can be evenly distributed among other servers - shards. The system can continue to scale transparently, adding new server power to it.
  • Built-in fault tolerance. Shardman automatically replicates the data of each shard to backup servers so that in the event of a failure of any of the nodes, it is transparent for users to redirect requests to another server.
  • Strict guarantees of data isolation and consistency. Shardman extends the PostgreSQL data consistency model for distributed systems and ensures transparent transaction operation for database clients.

File:Aquote1.png
In the information systems of large companies or banks, we approach high transaction loads approaching the ceiling of the capabilities of traditional DBMS. In such cases, horizontal scalability cannot be dispensed with. In response to such customer needs, we have released Shardman - a DBMS that will be able to provide horizontal scaling of OLTP databases in strict compliance with ACID requirements (atomicity, consistency, isolation and reliability), - said Ivan Panchenko, Deputy General Director, co-founder of Postgres Professional.
File:Aquote2.png

According to the developer, Shardman is suitable for cases when:

  • There are so many users that one server cannot cope with so many connections;
  • The write load is so large (OLTP system) that one server cannot cope with it;
  • There is so much data that it does not fit on one server: neither in memory nor on disk;
  • Large data processing required in parallel (OLAP system);
  • The application has complex logic on the DBMS side, as a result of which a lot of processor time is consumed.

Additional features: transparent data management, application acceleration, incremental backup, and data compression Shardman is based on PostgreSQL 14, but is equipped with additional features for large installations. Among the main advantages of DBMS:

  • Transparent data handling. The client, connecting to any node of the distributed system, gains access to all data stored in the system.
  • An interconnect mechanism that cuts off redundant TCP sessions between charms, reduces network load, and reduces resource competition.
  • Speed up applications that have complex logic on the DBMS side and increase the total TPS of the entire DBMS.
  • Additional features of Postgres Pro Enterprise DBMS: CFS data compression mechanism, incremental page-level backup, PTRACK backup mechanism and pgpro_stats extension.