credativ® Blog
Here you will find interesting news about industry-specific topics and us.
Categories
Category
Tag: planetpostgresql
06 July 2026
Replication Deadlock Bug in Current Postgres Releases 14-16
Replication Deadlock Bug in Current Postgres Releases 14-16 The current minor releases of Postgres versions 14-16 (14.23, 15.18 and 16.14, released on May 14th) introduced a regression that can lead to a MultiXactOffsetSLRU deadlock during transaction log (WAL) replay in certain circumstances. The bug was (to our knowledge) first reported in Bug#19490 on May 20th […]
26 May 2026
The PostgreSQL Conference HOW2026 in Jinan, China
At the end of April, I had the incredible opportunity to represent credativ on the HOW2026 (Hello Open-source World), the PostgreSQL & IvorySQL Eco Conference in Jinan, China. IvorySQL is a Chinese fork of PostgreSQL with extended Oracle compatibility. In recent years, it has been gaining popularity not only in China. The conference brought together […]
06 January 2026
Dissecting PostgreSQL Data Corruption
PostgreSQL 18 made one very important change – data block checksums are now enabled by default for new clusters at cluster initialization time. I already wrote about it in my previous article. I also mentioned that there are still many existing PostgreSQL installations without data checksums enabled, because this was the default in previous versions. […]
15 December 2025
PostgreSQL 18 Asynchronous Disk I/O - Deep Dive Into Implementation
PostgreSQL 17 introduced streaming I/O – grouping multiple page reads into a single system call and using smarter posix_fadvise() hints. That alone gave up to ~30% faster sequential scans in some workloads, but it was still strictly synchronous: each backend process would issue a read and then sit there waiting for the kernel to return […]
05 December 2025
A deeper look at old UUIDv4 vs new UUIDv7 in PostgreSQL 18
In the past there have been many discussions about using UUID as a primary key in PostgreSQL. For some applications, even a BIGINT column does not have sufficient range: it is a signed 8‑byte integer with range −9,223,372,036,854,775,808 to +9,223,372,036,854,775,807. Although these values look big enough, if we think about web services that collect billions […]