4. 1C improvements#
4. 1C improvements #
4.1. Core #
The problem of light locks with a large number of simultaneous DBMS connections has been solved.
The maximum size of data in table cells supported by the pg_dump module has been increased from 1 GB to 2 GB.
The values of the parameters have been changed, which, with default values, could lead to a deterioration in 1C performance.
4.2. Planner #
Optimized execution of queries using aggregate functions by changing the order of the grouping fields.
Improved prediction of table joins with multi-column indexes, which allows you to get a more accurate estimate of the number of rows and select the optimal query plan operator.
Caching of temporary tables has been optimized by reducing the list of invalidations.
Various operations with the list of columns used in the query have been optimized to reduce the overhead of executing queries and optimize memory usage.
Query execution has been optimized by highlighting common conditions for
ORandANDoperations inWHEREexpressions, in order to speed up filtering at the early stages of their processing.Execution of queries using the
IN (&Array Of Values)construct has been accelerated. For more information, see the article Solving the Values problem in Postgres.Fixed an error of incorrect evaluation of rows as a result of joining several tables, when 0 rows were selected from one table and additional conditions were imposed on the result of the connection.
4.3. Modules #
Logical replication slots are supported for the database copy mechanism in dbcopies_decoding.
The
SELECT FASTTRUNCATEfunction, designed to truncate temporary tables, has been accelerated in fasttrun. For more information, see the article Temporary tables and SELECT FASTTRUNCATE.The execution of queries using temporary tables that were created from the table of values passed to the query as a parameter has been accelerated in online_analyze. For more information, see the article 1C and the Tantor DBMS: the history of one implementation.