PostgreSQL 18 Introduces Pipelining Support in psql Client
By
tanelpoder
Pure flour-power. Hearty enough to carry you through lunch.
Summary
This article explains pipelining in PostgreSQL 18, a client-side feature that allows sending multiple queries to the server without waiting for previous results, thereby increasing throughput. Pipelining has been possible since PostgreSQL 7.4 (2003) but became more accessible through libpq in PostgreSQL 14 (2021). With PostgreSQL 18, the psql client now includes built-in pipelining support, which can significantly speed up client-server communication by reducing network latency and improving concurrency.
Key quotes
· 4 pulledPipelining is a client-side feature supported by the network protocol that basically consists of not waiting for the results of previously sent queries before sending the next.
Pipelining is possible since version 7.4 (released in 2003), which introduced the extended query protocol.
But it's only since 2021, with PostgreSQL 14, that it can be used through libpq, the client-side C library.
With PostgreSQL 18, the psql client version 18 comes with pipelining, which can speed up client-server communication.
You might also wanna read
PostgreSQL Double Buffering: Why OS RAM and Buffer Cache Compete and How the 25% Rule Helps
This article explains the problem of double buffering in PostgreSQL, where the OS filesystem cache and PostgreSQL's shared_buffers both cach
Analyzing PostgreSQL Database Workloads: Read-Heavy vs Write-Heavy Patterns and Optimization Strategies
This technical blog post explains how to determine if a PostgreSQL database is read-heavy or write-heavy and provides optimization strategie
PostgreSQL work_mem Configuration Pitfalls: How Low Memory Settings Can Cause Catastrophic Outages
The article discusses a critical PostgreSQL database performance issue where a production cluster with 2 TB of RAM was killed by the OOM (Ou
mydbanotebook.org·2mo ago
Optimizing Top K Query Performance in PostgreSQL: Challenges and Solutions
This technical article examines the challenges of optimizing Top K queries in PostgreSQL databases, where 'Top K' refers to retrieving the K
paradedb.com·2mo ago
Optimizing Geospatial SQL Queries with H3 Indexes for 400× Performance Gains
The article explains how to dramatically speed up geospatial SQL queries (geo joins) using H3 indexes. It describes the performance problems
floedb.ai·3mo ago
Performance Optimization: Replacing Protobuf with Direct C-to-Rust Bindings in PgDog PostgreSQL Proxy
The article details how PgDog, a PostgreSQL proxy written in Rust, replaced Protobuf serialization with direct C-to-Rust bindings to achieve
pgdog.dev·4mo ago