postgresql

The article provides a byte-by-byte analysis of PostgreSQL's VACUUM process at the page level, using pageinspect to show how dead tuple space is reclaimed.

This blog post explains why PostgreSQL databases are vulnerable to OOM killer and how using strict memory overcommit can prevent catastrophic outages. It also discusses a kernel bug and heuristics for setting the proper overcommit limit.

PL/CBMBASIC is a PostgreSQL procedural language extension that integrates the original Commodore 64 BASIC V2 interpreter, allowing users to write database functions in BASIC with line numbers. It emulates the 6502 interpreter in C, provides validation for BASIC naming constraints, and supports OUT parameters by reading the emulated variable table.

PostgreSQL 19 introduces kernel asynchronous reads via io_uring, enabling direct asynchronous buffered I/O for improved performance without dedicated worker processes.

This article discusses common pitfalls in database partitioning, particularly the mistake of partitioning by a date column that forces queries to include a date filter. It proposes partitioning by the primary key instead and using a background service to manage partition boundaries, thus avoiding the need to modify application code.

PostgreSQL 19 beta introduces key features like REPACK CONCURRENTLY, partition splitting and merging, and enhanced logical replication, offering practical improvements for production database management.

Report on the June 2026 ISO/IEC WG3 meeting in Stockholm, detailing the acceptance of new SQL features such as QUALIFY, INSERT BY NAME, and SELECT list EXCLUDE into the standard draft, with implications for PostgreSQL.

A technical article exploring PostgreSQL internals, covering the logical and physical structure of database clusters, databases, tables, system catalogs, and object identifiers (OIDs).

pg_plan_advice is a PostgreSQL module that allows users to influence and stabilize query plan choices by specifying plan advice using a mini-language. It helps in controlling join order, scan methods, and other planner decisions, but overriding planner defaults can backfire if data distribution changes.

Gjallarhorn is a from-scratch web framework for the Odin programming language, providing an HTTP server, router, middleware, template engine, and ORM with PostgreSQL support, all with no external dependencies.

A detailed technical guide explaining how PgBouncer works as a PostgreSQL connection pooler, covering its pooling modes, production deployment, and common pitfalls.

A detailed guide on using PostgreSQL as a single database to handle all aspects of a financial application, including schema design, state machines, triggers, and performance optimization.

This article explains how TimescaleDB's hypercore engine achieves up to 98% compression for time-series data using columnar storage and specialized algorithms like delta encoding and Gorilla XOR, and contrasts it with PostgreSQL's TOAST.

This post compares write-heavy sysbench performance of modern PostgreSQL (versions 15-19) and MySQL 8.4 on a large server, finding that InnoDB generally outperforms PostgreSQL on write throughput and shows less variation.

PostgreSQL 19 is finally introducing native temporal table support following the SQL:2011 standard, replacing the old manual approach with exclusion constraints. The article explains the limitations of the current method and the long-awaited benefits of the new feature.

A hands-on introduction to PostgreSQL using annotated SQL examples, covering basics to advanced topics.

PostgreSQL documentation introduces property graphs, a SQL/PGQ feature that allows querying relational data using graph pattern matching syntax, defined as read-only views over tables.

Microsoft open sourced pg_durable, a PostgreSQL extension that enables durable execution of long-running SQL functions with automatic checkpointing and fault-tolerant resumption.

Postgres 19 introduces query hints via new contrib modules pg_plan_advice and pg_stash_advice, ending a long-standing community debate and providing DBAs with an escape hatch for optimizer edge cases.

This article argues that using weaker database isolation levels as default is a form of premature optimization, and recommends serializable isolation level unless the DBMS already defaults to it. It cites real examples of concurrency bugs leading to financial losses.