The Error This error is misleading. It usually does not mean your server is out of RAM in the way people expect. It means that when PostgreSQL’s postmaster tried to fork() a new backend process to serve your connection, the…
Logical replication in PostgreSQL is wonderfully flexible — and wonderfully easy to misdiagnose. When something goes wrong, the symptom is almost always the same (“the subscriber is behind”), but the cause can live in any of half a dozen places:…
Part 1 — Article: Understanding pglogical What is pglogical? pglogical is a PostgreSQL extension developed by 2ndQuadrant (now part of EDB) that provides logical replication between PostgreSQL databases. Unlike physical (streaming) replication, which copies binary WAL data block-for-block, logical replication…
pg_top is a real-time monitoring utility for PostgreSQL, similar to the Linux top command. It allows DBAs and database engineers to monitor PostgreSQL backend processes, active SQL statements, resource consumption, and database activity in real time. Installing pg_top RHEL /…
In the world of PostgreSQL performance tuning, work_mem is one of the most frequently misunderstood parameters. Many administrators assume it represents a total memory limit for a database session or a single query, but in reality, its impact is much…
Imagine you are managing a multi-terabyte database, but only a fraction of that data is actually powering your application’s real-time performance. Without knowing which tables and indexes are “hot”—meaning frequently accessed and ideally stored in memory—you are essentially flying blind…
In PostgreSQL, the memory consumed by a single connection running a sequence of four SQL statements is not a simple cumulative total. Instead, it is determined by a combination of fixed process overhead, local memory allocations, and shared memory mappings.…
Monitoring memory consumption is a fundamental task for any PostgreSQL administrator. Unlike simple applications, PostgreSQL uses a sophisticated memory architecture that splits resources between a large shared pool and smaller, session-local areas for specific tasks like sorting and joining. Understanding…
If you are managing a PostgreSQL database, you likely have routine tasks that need to run on a schedule. Whether it is refreshing materialized views, deleting old session data, archiving logs, or running routine VACUUM operations, doing these things manually…
Managing large-scale databases often requires table partitioning, a technique where one large logical table is split into several smaller physical pieces. In PostgreSQL, the partitioned table itself is a “virtual” table that holds no data; instead, the data is stored…
