Amit Langote's posts

Postgres: TupleTableSlot as a batch container April 23, 2026 I’ve been working on adding batched execution to the Postgres executor.

Postgres: faster foreign key checks April 22, 2026 In an earlier post I described how foreign key enforcement works in Postgres.

Work: blocking time April 21, 2026 I’ve been noticing a pattern in my own work that I want to write down before I forget it or start rationalizing it into something cleaner than it actually is.

Postgres: one thread, one project April 12, 2026 I’ve been working on the pruning-aware partition locking patch off and on since 2022.

Postgres: pruning-aware partition locking, rethought April 5, 2026 In my last post I described a redesign of the pruning-aware partition locking patch that had been reverted from Postgres 18.

Postgres: cached plan partition locking bottleneck March 27, 2026 In two earlier posts (one, two), I described performance problems that arise when using prepared statements with partitioned tables.

Postgres: what to work on March 23, 2026 There are broadly two kinds of work one can do in the PostgreSQL project.

Postgres: executor batching, follow up March 8, 2026 About seven months ago I wrote a post sketching what executor batching in Postgres might look like and what it might achieve.

Postgres: how foreign keys work March 7, 2026 Foreign key constraints are one of those features that most people who’ve used a relational database take for granted.

Postgres: executor bottlenecks July 08, 2025 I wrote this post to expand on the first slide of a talk I gave recently at PGConf.in 2025 and then again at POSETTE 2025, covering executor performance improvements in PostgreSQL.

Postgres: planner internals (data structures and flow) July 08, 2025 Query planning in Postgres is often described as finding the cheapest execution path, and that is true at a high level, but the planner also has to guarantee correctness along the way –…

Postgres: more on performance of prepared statements with partitioning Nov 24, 2022 In a previous post, I described some performance problems when using prepared statements with partitioning due to excessive locking of partitions, causing a bottleneck as…

Postgres: on performance of prepared statements with partitioning May 16, 2022 Prepared statements (aka parameterized queries) suffer when you have partitioned tables mentioned in them.

Postgres: update statement will work differently in v14 June 8, 2021 Long story short, Tom Lane committed a few changes (commmits 86dc90056d, c5b7ba4e67a, a1115fa0782) to the v14 development branch that will help update and delete queries run little a bit…

Postgres: where is the data June 29, 2020 Postgres stores the data that one inserts into tables in files.

Postgres: partitioned tables can now be replicated …a bit more conveniently May 14, 2020 If your shop uses logical replication to selectively replicate tables between two PostgreSQL clusters and you also happen to rely on partitioning for some of these ta…

Postgres: caches and invalidation June 14, 2019 The other day, while debugging a patch to fix a memory leak bug in Postgres 12, I got to learn quite a bit about the caches that are used internally in Postgres and the internal machanics of invalidating them