Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for PostgreSQL
  • Getting started
    • All tutorials
    • Creating a PostgreSQL cluster for 1C
    • Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster
    • Exporting a database to Yandex Data Processing
    • Searching for cluster performance issues
    • Performance analysis and tuning
    • Setting up a connection from a Serverless Containers container
    • Delivering data to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for YDB using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for Apache Kafka® using Debezium
    • PostgreSQL change data capture and delivery to YDS
    • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Transferring data from Yandex Object Storage using Yandex Data Transfer
    • Configuring a fault-tolerant architecture in Yandex Cloud
    • Status monitoring of geographically distributed devices
    • Writing load balancer logs to PostgreSQL
    • Creating an MLFlow server for logging experiments and artifacts
    • Working with data using Query
    • Federated data queries using Query
    • Fixing string sorting issues after upgrading _glibc_
    • Writing data from a device into a database
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Issue criticality
  • Technical solution
  • How it works
  • Verification
  • Recommendations when upgrading Ubuntu to 18.04
  1. Tutorials
  2. Fixing string sorting issues after upgrading _glibc_

Fixing string sorting issues in PostgreSQL after upgrading glibc

Written by
Yandex Cloud
Updated at April 25, 2025
  • Issue criticality
  • Technical solution
    • How it works
    • Verification
  • Recommendations when upgrading Ubuntu to 18.04

The Ubuntu 18.04 version of the glibc (GNU C) library contains significant changes in the string sorting rules. This change affects the way the data is displayed and the structure of indexes in PostgreSQL, which may violate the uniqueness of the primary key.

For example:

CREATE TABLE t (id int, str text PRIMARY KEY);
INSERT INTO t VALUES (1, 'yndkpx'), (2, 'ynd_kpx'), (3, 'ynd-kpx'), (4, 'kpx');

Sort result in SELECT * FROM t ORDER BY str; output:

  • On Ubuntu 14.04:

     id |   str
    ----+---------
      1 | yndkpx
      2 | ynd_kpx
      3 | ynd-kpx
      4 | kpx
    
  • On Ubuntu 18.04:

     id |   str
    ----+---------
      3 | ynd-kpx
      2 | ynd_kpx
      1 | yndkpx
      4 | kpx
    

Issue criticalityIssue criticality

Changing the sorting order has the following consequences:

  • Violation of PRIMARY KEY uniqueness. PostgreSQL allows insertion of duplicates:

    INSERT INTO t VALUES (5, 'ynd_kpx');
    INSERT 0 1  -- The operation is successful, which is a violation
    
  • Incorrect operation of indexes:

    Checking via amcheck:

    CREATE EXTENSION IF NOT EXISTS amcheck;
    SELECT bt_index_check('t_pkey');
    

    Result:

    ERROR:  item order invariant violated for index "t_pkey"
    DETAIL:  Lower index tid=(1,1) (points to heap tid=(0,1)) higher index tid=(1,2) 
    (points to heap tid=(0,5)) page lsn=0/1665F88.
    
  • Changing string comparison results:

    -- Ubuntu 14.04:
    SELECT '1-1' < '11';
    
     ?column? 
    ----------
     f
    
    -- Ubuntu 18.04:
    SELECT '1-1' < '11';
    
     ?column? 
    ----------
     t
    

Technical solutionTechnical solution

The solution is implemented as an mdb-locales package, which includes:

  • libmdblocales library for uploading locales.
  • Patch for PostgreSQL.
  • Fixed locales from the previous glibc version.

How it worksHow it works

mdb-locales provides interception of locale system calls followed by their redirection to the library, which stabilizes the sorting behavior:

-- After installing mdb-locales:
SELECT * FROM pg_collation WHERE collprovider='c';

Result:

  oid  |  collname  | collnamespace | collowner | collversion
-------+------------+---------------+-----------+-------------
 12547 | en_US.utf8 |            11 |        10 | 2.27
 12548 | en_US      |            11 |        10 | 2.27

VerificationVerification

Checking for correct operation after installing mdb-locales:

-- Checking uniqueness of PRIMARY KEY
INSERT INTO t VALUES (5, 'ynd_kpx');

ERROR:  duplicate key value violates unique constraint "t_pkey"

-- Checking index integrity
SELECT bt_index_check('t_pkey');

 bt_index_check 
---------------
               
(1 row)

Recommendations when upgrading Ubuntu to 18.04Recommendations when upgrading Ubuntu to 18.04

  1. Before the upgrade:

    • Create a full backup of your data.
    • Audit the indexes.
    • Install and configure mdb-locales.
  2. After the upgrade:

    • Perform index checks via amcheck.
    • Test critical queries with sorting.
    • Verify unique restrictions.

Warning

Upgrading glibc may violate fundamental guarantees of the database. You need to perform a full test after upgrading the system.

Was the article helpful?

Previous
Federated data queries using Query
Next
Writing data from a device into a database
© 2025 Direct Cursus Technology L.L.C.