Sammlung von Newsfeeds

Christophe Pettus: All Your GUCs in a Row: max_pred_locks_per_page and max_pred_locks_per_relation

Neues vom PostgreSQL Planet - vor 2 Stunden 18 Minuten
PostgreSQL's serializable isolation remembers what each transaction reads with limited shared memory, so it trades tuple locks for page locks, then page locks…

Bruce Momjian: The Promise of Non-Volatile Memory

Neues vom PostgreSQL Planet - 21. September 2026 - 21:00

Relational databases like Postgres provide many unique features, specifically atomicity, consistency, isolation, and durability (ACID), but providing durability has always been a challenge. Though computers originally used non-volatile magnetic-core memory, the past five decades have been dominated by computer architectures where CPU-accessible memory is volatile, and OS-accessible storage is non-volatile/durable.

Cornelia Biacsics: Contributions for week 37

Neues vom PostgreSQL Planet - 21. September 2026 - 9:07

On 16 September 2026, the Postgres Meetup for All user group met, organized by Elizabeth Christensen and Ryan Booz. Ryan Booz and Greg Potter delivered a talk.

Christophe Pettus: All Your GUCs in a Row: max_parallel_apply_workers_per_subscription

Neues vom PostgreSQL Planet - 21. September 2026 - 3:00
Parallel apply workers speed up logical replication of large transactions—but only if you have enough of them.

Christophe Pettus: All Your GUCs in a Row: max_parallel_workers and max_parallel_workers_per_gather

Neues vom PostgreSQL Planet - 20. September 2026 - 3:00
Neither of these parameters means what its name says. max_parallel_workers_per_gather is the most workers the planner is allowed to request for one plan node, and the planner usually requests fewer. max_parallel_workers is documented as a limit for the whole cluster, and it is enforced by compari…

Henrietta Dombrovskaya: Major updates to pg_acm

Neues vom PostgreSQL Planet - 20. September 2026 - 2:16

I did it! The most important thing I anticipated after leaving DRW was having more time for important work, and one of the top items on my to-do list was the pg_acm update.

I already knew about two dozen bugs I needed to fix; several new functions people asked about. In addition, I had several conceptual changes in mind. Do you know how disturbing it is when you know you need to do something, and you can’t focus on that “something” because other things, less important but more urgent, keep popping up?

Christophe Pettus: All Your GUCs in a Row: max_parallel_maintenance_workers

Neues vom PostgreSQL Planet - 19. September 2026 - 3:00
max_parallel_maintenance_workers is a ceiling, and most of the time something lower gets there first. It caps the number of parallel workers a single utility command may start. The default is 2, the context is user, and the range is 0 to 1024, with 0 turning parallel maintenance off. Raising it i…

Mark Wong: Sizing an OLTP TPC-E-like workload, Part 1

Neues vom PostgreSQL Planet - 19. September 2026 - 2:41

I used AI tools to size an OLTP workload on an EC2 system, with DBT-5, a TPC-E-like fair-use implementation. I provided a systematic and mechanical plan for running a series of tests to determine what the appropriate scale factor is on a system.

Ruohang Feng: PostgreSQL's Chinese Error Messages Were Seven Years Stale. Not Anymore.

Neues vom PostgreSQL Planet - 19. September 2026 - 2:00
Never set your PostgreSQL locale to zh_CN — that old rule expires with PostgreSQL 19. The Chinese message catalogs went seven years untouched and nearly got dropped from the release. A bone nobody could chew through in seven years, finished in seven days.

Shaun Thomas: Looking Forward to Postgres 19: Epilogue

Neues vom PostgreSQL Planet - 18. September 2026 - 18:52

The future of Postgres is bright. So bright in fact, that I spent almost a dozen posts expounding on the upcoming features it would bring, with veritable stars in my eyes. Unfortunately, while I was out counting my chickens, it would seem some of these exciting new features failed to hatch.How, and perhaps more importantly why that happened, deserves some investigation.

Jimmy Angelakos: postgres.scot is live, August PostgresEDI meetup

Neues vom PostgreSQL Planet - 18. September 2026 - 10:30
postgres.scot is live

Postgres events in Scotland now have a permanent address: postgres.scot

Christophe Pettus: All Your GUCs in a Row: max_notify_queue_pages

Neues vom PostgreSQL Planet - 18. September 2026 - 3:00
Nobody asked for max_notify_queue_pages. It exists because a limit that used to enforce itself stopped doing so, and something had to take its place. LISTEN/NOTIFY runs on a single queue for the whole cluster, stored as SLRU pages under pg_notify/ in the data directory. Through PostgreSQL 16 that…

Mikhail Shytsko: Your Agent Is Reading Someone Else's Tenant

Neues vom PostgreSQL Planet - 18. September 2026 - 2:00

Two client connections, opened one after the other through PgBouncer transaction mode, asked the same database whose rows they were allowed to see, and the second one got the first one's answer. It had set nothing, it had never met the first caller, and the rows it read belonged to that caller's tenant. Any runbook that keeps a tenant key in a session variable sits one pooler away from this, and since 28 July the MCP protocol carries no session of its own, so a tool call from an agent arrives in this shape by default.

Joshua Drake: pgColumnar 1.0-alpha4 released

Neues vom PostgreSQL Planet - 17. September 2026 - 21:18
SourceDocsProduct page2026-09-17pgColumnar 1.0-alpha4 release notesRelease date: 2026-09-17 Previous release: 1.0-alpha3 (2026-09-02)pgColumnar is a columnar table access method for PostgreSQL. This is the fourth alpha. Its theme is layout and skipping. A table can now be laid out on the Hilbert curve, which keeps neighbouring keys closer together than Z-order does. A star-schema join now skips fact-table groups and …

Christophe Pettus: The Call Is Coming From Inside the Session

Neues vom PostgreSQL Planet - 17. September 2026 - 18:00
Role-level timeouts and read-only flags sound safe until you realize the session can change them in one statement.

Muhammad Aqeel: Flexible Deployment: What Enterprise-Grade Self-Hosting Actually Demands

Neues vom PostgreSQL Planet - 17. September 2026 - 17:31

Ask a database vendor about on-prem and you'll usually get a one-line answer: 'we're open source, you can just self-host it.' For a hobby project, fine. For an enterprise, that line rarely survives contact with production. And enterprises want on-prem more than ever right now, largely because of AI. Running open models on hardware you own is far cheaper than renting inference by the token, and in a regulated industry, keeping data where you control it isn't optional.

Gülçin Yıldırım Jelínek: Postgres week in the Netherlands: PGDay Lowlands & Percona Live 2026

Neues vom PostgreSQL Planet - 17. September 2026 - 16:02

Last week, I spent three days in the Netherlands and gave two talks at two conferences: a lightning talk at PGDay Lowlands in Utrecht on Thursday, September 10, and a session at Percona Live in Amsterdam on Friday, September 11\. In this blog post, I’m going to share my notes from both.

Postgres Monitoring for SQL Server DBAs: Statistics and Logs 101

Pganalyze Blog RSS Feed - 17. September 2026 - 14:00

As a SQL Server developer and DBA learning Postgres, it’s easy to expect that the information you need for meaningful query and performance tuning will be readily available. For years (decades, maybe) you’ve learned the DMVs, set up Extended Events sessions, relied on Query Store, and regularly run Ola Hallengren’s maintenance scripts and Brent Ozar’s First Responder Kit.

Ryan Booz: Postgres Monitoring for SQL Server DBAs: Statistics and Logs 101

Neues vom PostgreSQL Planet - 17. September 2026 - 14:00

As a SQL Server developer and DBA learning Postgres, it’s easy to expect that the information you need for meaningful query and performance tuning will be readily available. For years (decades, maybe) you’ve learned the DMVs, set up Extended Events sessions, relied on Query Store, and regularly run Ola Hallengren’s maintenance scripts and Brent Ozar’s First Responder Kit.

Radim Marek: Row locks at the page level

Neues vom PostgreSQL Planet - 17. September 2026 - 7:00

In PostgreSQL, every tuple starts with 23-byte header, and the first eight bytes are two transaction IDs. t_xmin for the transaction that created the row and t_xmax for the one that deleted or updated it. That is the visibility story covered in PostgreSQL MVCC, Byte by Byte. For now we have discussed t_xmax acting as the delete marker.

Seiten