Picodata DBMS

Main article: Database Management System (DMS)

2025

Picodata 25.3 with secure connection when accessing an external LDAP server

Picodata has released an updated version of the Picodata DBMS - Picodata 25.3. The upgrade includes advanced SQL capabilities, an automatic data schema update mechanism, and increased cluster stability. The developer announced this on July 30, 2025.

Picodata 25.3 implements automatic updating of the data scheme when the instances switch to this Picodata release. This mechanism takes into account the changes made in system tables and retains backward compatibility when updating to the next release of the DBMS: when transferring the cluster to this version of Picodata, the necessary DDL/DML commands will be executed without administrator intervention, and the internal functions required in the new scheme will also be created automatically.

SQL features in Picodata have been added to the release, in particular:

• NULLS FIRST/LAST support when sorting query results (ORDER BY)
• handling conflicts when inserting data into global tables (INSERT INTO... ON CONFLICT DO FAIL/REPLACE/NOTHING);
• Built-in LAST_VALUE window function ()
• the% operator to determine the remainder of the modulo division for integers;
• possibility of determining the leader of the raft group through the functions pico_raft_leader_id () and pico_raft_leader_uuid ();
• The ability to determine the version of the current instance using the version () function.
• compatibility change: Instead of the scalar function instance_uuid (which is now deprecated), it is recommended that you use the new pico_instance_uuid function.

Picodata now supports a secure connection when accessing an external LDAPto the server-. When connecting via a protocol PostgreSQL (for example, using the psql client authentications) with the LDAP method, you can use - TLS(enciphering provided that it is enabled on LDAP-). server On the Picodata side, this will require setting the values ​ ​ of the three environment variables.

The instance.pg.advertise parameter has been added - the public address of the server for connecting using the PostgreSQL protocol. By default, its value corresponds to instance.pg.listen. This parameter is useful in a situation where the instance is accessible from the outside at an address other than the address on the internal network.

The Picodata team continues to develop the webui component for Picodata. In Picodata 25.3, the web interface not only looks better, it has also become more convenient and informative:

• the Cluster ID panel displays more useful information, including a list of enabled plugins;
• The instance details view now contains the PostgreSQL connection address.

When connecting the plugin to the Picodata cluster, minor versions of the plugin and instance are now allowed to differ (for example, the plugin assembled for version 25.3.1 will work in Picodata 25.3.2).

A complete list of innovations and a list of fixed bugs are available in the CHANGELOG document.

A new version of the Picodata role for Ansible has been released, which is compatible with Picodata 25.3. Role Changes:

• When assembling information on failure (crash_dump tag), you can exclude the assembly of snap- and xlog-files.
• added the ability to execute lua commands on cluster instances (command tag);
• fixed work with several plugins in the inventory file and a number of other errors.

In Release 25.3, we focused on making the system even more stable and secure - especially for our critical information infrastructure operators. The reliability of Picodata installations is our priority, and current updates strengthen this foundation, "said Anna Yermanok, CEO of Picodata.

Compatibility with Luxms BI

Luxms BI is compatible with the domestic Picodata DBMS. Luxms announced this on April 2, 2025. Read more here.

FSTEC 4 Level of Trust Certification

Picodata DBMS received a certificate of compliance with the FSTEC of Russia in 4 levels of trust (certificate No. 4917 dated March 3, 2025). The company announced this on March 14, 2025.

Compared to Class 6 Protection/Trust Level, Class 4 places additional requirements on the security model, software development processes, and its vulnerability testing and ensures that there are no hidden features in the Picodata software product.

This is an important milestone for Picodata, since our product is one of the few examples of fully domestic software that meets the information protection requirements established by the FSTEC of Russia for DBMS, "said Anna Yermanok, CEO of Picodata.

FSTEC certification provides customers with confidence in qualified and operational technical support in Russia and guarantees stable operation of information systems built using Picodata DBMS.

The product is included in the state register of the certification system for information protection tools according to information security requirements on March 3, 2025. The certificate is valid until March 3, 2030.

2024

Developing a Connector for Integration with Arenadata Catalog

The DataCatalog team (part of the Arenadata Group) has completed the development of a connector that provides compatibility between the Arenadata Catalog (ADC) product and the Picodata DBMS. Arenadata announced this on November 26, 2024. Read more here.

Obtaining the certificate of FSTEC of Russia of the 6th protection class

Picodata DBMS, developed by Picodata (part of Arenadata Group), has received a certificate of compliance with the information security requirements of the FSTEC of Russia for database management systems (DMS) of the 6th protection class. Certificate No. 4862 was issued on October 4, 2024 in accordance with the order of the FSTEC of Russia dated April 14, 2023 No. 64. The developer announced this on October 9, 2024.

The certificate confirms that the Picodata DBMS meets a number of key security requirements, such as access control, user identification and authentication, data integrity control, security event logging, data backup and recovery, availability, memory cleanup, performance maintenance, and software environment limitation. In addition, the certification confirms the implementation of secure software development standards.

For our company, obtaining an FSTEC certificate in Russia is an important milestone, since Picodata DBMS is one of the few examples of fully Russian software that meets information protection requirements. This fact provides customers with confidence in qualified and operational technical support in Russia. And also guarantees the stable operation of information systems built using Picodata DBMS, said Konstantin Osipov, co-founder and CTO of Picodata.

As of October 2024, Picodata is working on obtaining a certificate of compliance with the requirements of the FSTEC of Russia of the 4th class of protection on the Picodata DBMS.