Skip to content
TILens What matters today in tech v0.3.0
Theme

Topic - Edition

PostgreSQL

11 items on 11 Sep 2026
Java PostgreSQL

Meet Jos Roseboom

JavaZone 2026 At the beginning of September, I participated in JavaZone for the third time and had the privilege of meeting a lot of passionate software developers willing to share their knowledge with the community. In…

Source: Vlad Mihalcea vladmihalcea
PostgreSQL

CERN PGDay 2027: Announcement and CfP

CERN PGDay 2027 Date: Friday, February 12, 2027 Location: CERN Campus, Geneva, Switzerland / Suisse Romande Language: English Organizers: Swiss PostgreSQL Users Group (SwissPUG) & CERN Format: Single-track (6–7…

Source: PostgreSQL News
PostgreSQL

Shaun Thomas: PG Phriday: The Folder That Ate the Publisher

Logical replication has been part of Postgres since version 10, and the syntax page that governs it is almost comically brief. wants a name, a connection string, a list of publications, and then it offers one innocuous…

Source: Planet PostgreSQL
PostgreSQL

Radim Marek: The unbearable lightness of one more index

Being "the database guy" comes with a lot of questions, and over the last eight months those questions changed. The repetitive ones disappeared, nobody asks how to avoid putting things in the database any more, and the…

Source: Planet PostgreSQL
PostgreSQL

Christophe Pettus: All Your GUCs in a Row: max_connections

max_connections is a memory budget and a circuit breaker wearing a capacity costume. It does not decide how many queries your server can run at once; the core count and the storage decide that, and they were decided…

Source: Planet PostgreSQL
PostgreSQL

Mikhail Shytsko: Your Agent Can Turn Off Its Own Kill Switch

A new agent needs a database login, so the role it logs in as gets the treatment every runbook recommends. Two ALTER ROLE lines go in, one capping how long a single statement may run and one making transactions…

Source: Planet PostgreSQL
PostgreSQL

Alexander Ioffe: Postgres runs your query fast exactly five times. Then it changes its mind. One prepared statement, twelve EXPLAIN ANALYZE runs on one connection, a plan change on run six, and why a single run could never have shown it.

A prepared statement ran in 274 ms for five executions and 2,319 ms from the sixth, on the same connection in the same minute. One EXPLAIN ANALYZE is a sample of size one and cannot see this; twelve in a row, with the…

Source: Planet PostgreSQL