credativ® Blog
Here you will find interesting news about industry-specific topics and us.
Categories
Category
12 January 2026
Foreman in IPv6-mostly and IPv6-only environments
Foreman is clearly rooted in an IPv4 world. You can see it everywhere. Like it does not want to give you a host without IPv4, but without IPv6 is fine. But it does not have to be this way, so let’s go together on a journey to bring Foreman and the things around it into […]
08 January 2026
Determining the Maximum CPU Model for Live Migrations in Proxmox Clusters with ProxCLMC
ProxCLMC – What is it? Live migration is one of the most powerful and frequently used functions in a Proxmox VE Cluster. However, it presupposes a requirement that is often underestimated: consistent CPU compatibility across all nodes. In real-world environments, clusters rarely consist of identical hardware where you could simply use the CPU type host. […]
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. […]
19 December 2025
credativ GmbH successfully certified according to ISO 27001 and ISO 9001
credativ GmbH, a specialized service provider for open source solutions, is solidifying its position as a strategic partner for security-critical IT infrastructures. Since December 15, the company has been officially certified according to the international standards ISO/IEC 27001:2022 (Information Security) and ISO 9001:2015 (Quality Management). Expertise from corporate structures – Agility as an independent company […]
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 […]
