Pull to refresh
64K+

Database Administration *

Everything about database administration

98,82
Rating
Show first
Rating limit
Level of difficulty
Format

PostgreSQL 19: CommitFest 2026-03 Part 5.4 (SQL, DEV1, DEV2)

Level of difficultyMedium
Reading time7 min
Reach and readers8.7K

We’re wrapping up our review of the March CommitFest for PostgreSQL 19. This fourth and final article in the series covers the changes related to SQL and to our DEV1 and DEV2 courses.

As a reminder, here’s the plan for our coverage of the final PostgreSQL 19 CommitFest:

Part 5.1 (QPT)

Part 5.2 (DBA1, DBA2)

Part 5.3 (DBA3, DBS)

Part 5.4 (SQL, DEV1, DEV2) – you are here 🙂

For the earlier CommitFests, see: 2025-07, 2025-09, 2025-11, 2026-01.

Read more

PostgreSQL 19: CommitFest 2026-03 Part 5.3 (DBA3, DBS)

Level of difficultyMedium
Reading time9 min
Reach and readers5.4K

We’re continuing our review of the March CommitFest for PostgreSQL 19. This third article in the series covers the changes related to our DBA3 and DBS courses.

As a reminder, here’s the plan for our coverage of the final PostgreSQL 19 CommitFest:

Part 5.1 (QPT)

Part 5.2 (DBA1, DBA2)

Part 5.3 (DBA3, DBS) – you are here 🙂

Part 5.4 (SQL, DEV1, DEV2)

For the earlier CommitFests, see: 2025-07, 2025-09, 2025-11, 2026-01.

Read more

PostgreSQL 19: CommitFest 2026-03 Part 5.2 (DBA1, DBA2)

Level of difficultyMedium
Reading time11 min
Reach and readers4.3K

We’re continuing our review of the March CommitFest for PostgreSQL 19. This second article in the series covers the changes related to our DBA1 and DBA2 courses.

As a reminder, here’s the plan for our coverage of the final PostgreSQL 19 CommitFest:

Part 5.1 (QPT)

Part 5.2 (DBA1, DBA2) – you are here 🙂

Part 5.3 (DBA3, DBS)

Part 5.4 (SQL, DEV1, DEV2)

For the earlier CommitFests, see: 2025-07, 2025-09, 2025-11, 2026-01.

Read more

PostgreSQL 19: CommitFest 2026-03 Part 5.1 (QPT)

Level of difficultyMedium
Reading time13 min
Reach and readers5K

We’re wrapping up our series of articles reviewing the changes in PostgreSQL 19. The previous articles covered the first four CommitFests: 2025-07, 2025-09, 2025-11, 2026-01.

Today we begin our review of the March 2026 CommitFest. Why «begin»? As in previous years, the March review is going to be a long one: the final CommitFest of the cycle is where many of the most important changes land. Such a review is hard not only to write but also to read all the way through 🙂. That’s why this time it’s split into four articles.

The first article covers everything related to query optimization, in other words, the topics of our QPT training course. The second will focus on changes more relevant to the DBA1 and DBA2 courses. The third will cover DBA3 and DBS. The fourth will look at new SQL features, as well as changes related to the DEV1 and DEV2 courses.

Read more

I Sent the Same PostgreSQL Traffic in Smooth and Bursty Patterns. Average Load Lied

Level of difficultyMedium
Reading time9 min
Reach and readers3.4K

After experimenting with connection pool behavior, I wanted to test another assumption that looks harmless on dashboards.

If two workloads have the same average request rate, are they really equivalent from the database point of view?

At first, it seems reasonable.

If one service receives 1,000 requests per second on average and another also receives 1,000 requests per second, both appear to place roughly the same load on PostgreSQL.

But averages remove timing.

And timing is exactly where queues appear.

So I built a controlled queueing simulation of a Go service talking to PostgreSQL through a connection pool.

This was not a benchmark of PostgreSQL itself. I deliberately kept the model simple because I wanted to isolate one variable: the arrival pattern.

The total amount of traffic stayed the same.

Only the timing changed.

One workload was smooth.

The other arrived in bursts.

The average RPS was identical.

The model behaved very differently.

Read more

I Kept the Same Database Load and Changed Only the Connection Pool Size. Bigger Stopped Helping

Level of difficultyMedium
Reading time9 min
Reach and readers3.8K

After my previous experiment with PostgreSQL latency, I kept thinking about one very simple fix.

If requests spend too much time waiting for a database connection, why not just increase the connection pool?

It sounds reasonable.

More connections should mean less waiting. Less waiting should mean lower request latency. And if the database still has spare capacity, increasing the pool should solve the problem almost for free.

That logic is correct up to a point.

What I wanted to find was where that point actually is.

So I kept the workload unchanged and varied only one parameter: the maximum number of simultaneous database operations allowed by the connection pool.

The result was not that larger pools were bad.

It was something less dramatic and more useful.

A larger pool helped a lot while the system was undersized.

Then, quite suddenly, it stopped helping.

Read more

When PostgreSQL Throughput Looks Fine but p99 Is Already Falling Apart

Level of difficultyHard
Reading time11 min
Reach and readers4.7K

A PostgreSQL service can keep processing almost the same number of requests per second while its slowest requests become several times worse. CPU may still look comfortable, query execution time may barely move, and throughput may remain almost flat. The problem can appear one layer earlier, inside the connection pool, where requests start waiting before PostgreSQL even sees them. This experiment shows how that happens and why p99 usually notices it long before RPS does.

Read more

When a perfect audit was too hard to use

Level of difficultyEasy
Reading time7 min
Reach and readers4.6K

Everyone loves security — until they have to configure it. The first version of our audit extension felt like a nuclear power plant control panel: infinitely flexible, but impossible to operate without a manual. We admitted defeat, listened to DBA complaints, and shipped version 2.0 — with event classes and configuration logic designed for humans, not just compilers.

This article tells the story of fixing our own mistakes and turning a “shelf-ware” product into a tool people actually use.

Read more

PGConf.Nepal 2026 invites you

Level of difficultyEasy
Reading time3 min
Reach and readers5K

From 18 to 21 November 2026, Nepal will host PGConf.Nepal 2026, the country’s fourth PostgreSQL conference. The previous events took place in 2018, 2023, and 2025. This year, the conference is expected to bring together a wider mix of participants, organisations, and countries.

Read more

How we choose LLMs and frameworks for AI agents

Level of difficultyEasy
Reading time10 min
Reach and readers4.4K

The journey from a single A100 in the cloud to an H200 cluster is not just a hardware upgrade — it’s a story of how an ML team stopped chasing “the one perfect model” and started building an ecosystem. When there are millions of lines of PostgreSQL C code under the hood and tasks range from hint-set generation to Graph-RAG, the model stops being a black box and becomes just another replaceable component. We explain how we rebuilt our stack around vLLM and MCP, why context management matters more than model weights, and how we made a 0.6B-parameter model perform on par with the giants using GRPO.

Read more

Excel Life Hacks That 'Experts' Don't Know

Level of difficultyEasy
Reading time5 min
Reach and readers1.5K

I watched my experienced finance colleague struggle with Excel for a whole hour. He's an Excel guru, has been working with it for 20 years. But when I saw how he was typing formulas, I couldn't help but show him a couple of simple tricks that blew his mind.

It was a problem of ignorance—ignorance of features that have been in Excel for years, saving hours of work, but which no one ever talks about.

That's why I'm writing this article, to gather the best life hacks and save precious seconds of your life.

Read more

Index page pruning in PostgreSQL

Level of difficultyEasy
Reading time11 min
Reach and readers1.3K

Page pruning (HOT cleanup) is an optimization allowing to efficiently remove old row versions (tuples) from table blocks. The freed space will be reused for new row versions. The only space occupied by row versions beyond the database's xmin horizon is reclaimed. This article examines the algorithm behind a similar optimization for indexes. If the xmin horizon is held back - by a long-running query or transaction - neither page pruning nor VACUUM can reclaim space, forcing new row versions to be inserted into different blocks. With the standard pgbench test, we demonstrate how significantly performance can degrade when the database horizon is held back, and we analyze the underlying causes. 

Read more

SQL Window Functions in Simple Terms with Examples

Reading time4 min
Reach and readers840

Hello everyone!

I want to note right away that this article is written exclusively for people who are just starting their journey in learning SQL and window functions. It may not cover complex applications of functions or use complicated definitions—everything is written in the simplest language possible for a basic understanding.

P.S. If the author didn't cover or write about something, it means they considered it non-essential for this article)))

For the examples, we will use a small table that shows student grades in different subjects. In the database, the table looks like this:

Read more

PostgreSQL for WMS: a DBMS selection strategy in the era of import substitution

Level of difficultyMedium
Reading time9 min
Reach and readers8.3K

Today we want to talk about choosing a DBMS for WMS not as a dry technical discussion, but as a strategic decision that determines the security, budget, and future flexibility of your business. This is not about "why PostgreSQL is technically better," but about why it has become the only safe, cost-effective, and future-proof solution for Russian warehouse systems in the new reality.

This is not just another database article. It is a roadmap for those who do not want to wake up one day with a paralyzed warehouse and multi-million fines due to a bad decision made yesterday. At INTEKEY we have gone this path deliberately, and today our WMS projects for the largest market players run on PostgreSQL. We know from experience where the pitfalls are and how to avoid them.

Read more