atlas news
    
Planet PostgreSQL
07  novembre     13h00
Elizabeth Garrett Christensen: Postgres Internals Hiding in Plain Sight
   Postgres has an awesome amount of data collected in its own internal tables. Postgres hackers know all about this - but software developers and folks working with day to day Postgres tasks often miss out the good stuff.The Postgres catalog is how Postgres keeps track of itself. Of course, Postgres...
06  novembre     19h00
Jimmy Angelakos: pg statviz 0.8 released with PostgreSQL 18 support
   I’m happy to announce release 0.8 of pg statviz, the minimalist extension and utility pair for time series analysis and visualization of PostgreSQL internal statistics. This release adds support for PostgreSQL 18, adapting to significant catalog view changes introduced in this release: I O...
    15h53
Jobin Augustine: PostgreSQL 13 Is Reaching End of Life. The Time to Upgrade is Now
   PostgreSQL 13 will officially reach End-of-Life (EOL) on November 13, 2025. After this date, the PostgreSQL Global Development Group will stop releasing security patches and bug fixes for this version. That means if you’re still running PostgreSQL 13, you’ll soon be on your own with no updates, no...
    13h00
Paul Ramsey: PostGIS Performance: Improve Bounding Boxes with Decompose and Subdivide
   In the third installment of the PostGIS Performance series, I wanted to talk about performance around bounding boxes.Geometry data is different from most column types you find in a relational database. The objects in a geometry column can be wildly different in the amount of the data domain they...
    10h53
Ian Barwick: PgPedia Week, 2025-10-26
   PostgreSQL 19 changes this week ALTER SUBSCRIPTION : REFRESH SEQUENCES syntax added error on null() added for checking if the input is the NULL value COPY TO now works with partitioned tables full text search : database default collation now used for parsing psql : Improve tab completion for large...
05  novembre     23h59
vignesh C: Seamless PostgreSQL subscriber upgrades: Preserving Logical Replication state
   Upgrading to a new major version of PostgreSQL has become faster and safer with pg upgrade, but for teams using logical replication, a persistent pain point remained: the state of their subscribers was lost, forcing a tedious and high-risk rebuild of their replication setups.
    14h13
Daniel Vérité: Producing UUIDs Version 7 disguised as Version 4 (or 8)
   When communicating UUID-v7 values to third parties, the creation dates inside them are leaked. In this post, let’s see how to encrypt the timestamp to solve that problem.
    13h30
Ian Barwick: PgPedia Week, 2025-10-19
   Due to an unfortunate recent visitation by the Virus of the Decade (so far), I have a backlog of these which I’m trying to work through, so in the remote chance anyone is waiting with bated breath for the newest editions, my apologies. Normal service will be resumed as soon as humanly possible....
    11h28
Henrietta Dombrovskaya: October PUG Recording
   Almost a month late, but I hope you enjoy it
    09h26
Chris Travers: NUMA, Linux, and PostgreSQL before libnuma Support
   PostgreSQL and NUMA, part 2 of 4This series covers the specifics of running PostgreSQL on large systems with many processors. My experience is that people often spend months learning the basics when confronted with the problem. This series tries to dispel these difficulties by providing a clear...
04  novembre     14h39
Deepak Mahto: PostgreSQL Partition Pruning: The Role of Function Volatility
   In one of our earlier blogs, we explored how improper volatility settings in PL pgSQL functions namely using IMMUTABLE, STABLE, or VOLATILE can lead to unexpected behavior and performance issues during migrations. Today, let’s revisit that topic from a slightly different lens. This time, we’re not...
    06h00
Hans-Juergen Schoenig: Counting Customers in PostgreSQL
   As a database consulting company, we are often faced with analytics and reporting related tasks which seem to be easy on the surface but are in reality not that trivial. The number of those seemingly simple things is longer than one might think, especially in the area of reporting The purpose of...
    05h56
Mayur B.: ALTER Egos: Me, Myself, and Cursor
   I pushed the most boring change imaginable, add an index. Our CI CD pipeline is textbook spin up a fresh DB, run every migration file in one single transaction, in sequential manner. If anything hiccups, the whole thing rolls back and the change never hits main. Foolproof autotests.Enter The Drama...
03  novembre     12h34
Hubert ’depesz’ Lubaczewski: Do you really need tsvector column?
   When using tsearch one usually, often, creates a tsvector column to put data in, and then create index on it. But, do you really need the index? I wrote once already that you don’t have to, but then a person talked with me on IRC, and pointed this section of docs: One advantage of the …...
    09h30
Josef Machytka: PostgreSQL 18 enables data checksums by default
   As I explained in my talk on PostgreSQL Conference Europe 2025, data corruption can be silently present in any PostgreSQL database and will remain undetected until we physically read corrupted data. There can be many reasons why some data blocks in tables or other objects can be damaged. Even...
02  novembre     20h45
Radim Marek: Beyond Start and End: PostgreSQL Range Types
   Beyond Start and End columns with PostgreSQL range types# One of the most read articles at boringSQL is Time to Better Know The Time in PostgreSQL where we dived into the complexities of storing and handling time operations in PostgreSQL. While the article introduced the range data types, there’s...
    13h32
Cornelia Biacsics: Contributions for week 44, 2025
   PostgreSQL received attention through the following contributions at Data Stack Conf 2025 on Oct 29, 2025: Speaker Radoslav Stanoev Pavlo Golub Là titia Avrot Valeria Bogatyreva Devrim Gündüz PostgreSQL Booth Staff Devrim Gündüz Pavlo Golub Gabriele Quaresima spoke at Cloud Native Bergen on Tuesday...
01  novembre     15h21
Dave Stokes: Migration From MySQL To PostgreSQL In Five Steps Using DBeaver
   nbsp;I wrote a post in my MySQL blog on migrating from MySQL to PostgreSQL using DBeaver. You can pass it along to your acquaintances who want to get off the Dolphin and on the Elephant. Not only will DBeaver move your tables and data, but you can compare them afterwards. In the post, I...
31  octobre     18h25
Antony Pegg: Meeting High Availability Requirements in Non-Distributed PostgreSQL Deployments
   High availability in PostgreSQL doesn’t always require a globally distributed architecture. Sometimes you need reliable failover and replication within a single datacentre or region. pgEdge Enterprise Postgres handles this scenario with a production-ready PostgreSQL distribution that includes the...
    13h00
Tomas Vondra: Don’t give Postgres too much memory
   From time to time I get to investigate issues with some sort of a batch process. It’s getting more and more common that such processes use very high memory limits (maintenance work mem and work mem). I suppose some DBAs follow the logic that more is better , not realizing it can hurt the...
    07h52
Umair Shahid: What Are Dirty Pages in PostgreSQL?
   PostgreSQL stores data in fixed size blocks (pages), normally 8 KB. When a client updates or inserts data, PostgreSQL does not immediately write those changes to disk. Instead, it loads the affected page into shared memory (shared buffers), makes the modification there, and marks the page as dirty....
30  octobre     23h59
Nikolay Samokhvalov: PostgresMarathon 2-011: Prepared statements and partitioned tables the paradox, part 3
   In #PostgresMarathon 2-009 and #PostgresMarathon 2-010, we explored why execution 6 causes a lock explosion when building a generic plan for partitioned tables the planner must lock all 52 relations because it can’t prune without parameter values.Today we’ll test what actually happens with...
    23h00
Paolo Melchiorre: Install PostgreSQL 18 on Ubuntu 25.10
   How-to guide for installing PostgreSQL version 18 on Ubuntu, after a fresh installation of version 25.10 (Questing Quokka).
29  octobre     23h59
Nikolay Samokhvalov: PostgresMarathon 2-010: Prepared statements and partitioned table lock explosion, part 2
   In #PostgresMarathon 2-009, we focused on Lock Manager’s behavior when dealing with prepared statements and partitioned tables. And observed a lock explosion in our simple synthetic example: from 8 locks (custom plans) during first 5 calls, to 52 locks (building generic plan) in the 6th call, to 13...
    11h59
Hubert ’depesz’ Lubaczewski: Waiting for PostgreSQL 19 - Add psql PROMPT variable for search path.
   On 28th of October 2025, Nathan Bossart committed patch: Add psql PROMPT variable for search path.   The new %S substitution shows the current value of search path. Note that this only works when connected to Postgres v18 or newer, since search path was first marked as GUC REPORT in commit...
    06h00
Cornelia Biacsics: Head of Marketing experiences PGConf.EU 2025 - A Riga Recap
   PostgreSQL Conference Europe 2025 in Riga has officially come to an end and what remains are the impressions, emotions, moments, and the incredible vibe that remind me why we do what we do. I met so many inspiring people, had conversations with some of my role models, and wore many hats throughout...
28  octobre     05h00
Nikolay Samokhvalov: PostgresMarathon 2-009: Prepared statements and partitioned table lock explosion, part 1
   In #PostgresMarathon 2-008, we discovered that prepared statements can dramatically reduce LWLock:LockManager contention by switching from planner locks (which lock everything) to executor locks (which lock only what’s actually used). Starting with execution 7, we saw locks drop from 6 (table 5...
    05h00
Hans-Juergen Schoenig: The Future of CYBERTEC and PostgreSQL
   For this second entry into our blog feature to celebrate 25 years of CYBERTEC, our CEO gave some interesting insights into what he expects of the future - for the company as well as PostgreSQL as a whole. CYBERTEC in another 25 years Interviewer: Let’s talk about the future. Where do you think you...
27  octobre     23h12
Jeremy Schneider: Explaining IPC:SyncRep - Postgres Sync Replication is Not Actually Sync Replication
   Postgres database-level “synchronous replication” does not actually mean the replication is synchronous. It’s a bit of a lie really. The replication is actually – always – asynchronous. What it actually means is “when the client issues a COMMIT then pause until...
    14h10
Robert Bernier: Troubleshooting PostgreSQL Logical Replication, Working with LSNs
   PostgreSQL logical replication adoption is becoming more popular as significant advances continue to expand its range of capabilities. While quite a few blogs have described features, there seems to be a lack of simple and straightforward advice on restoring stalled replication. This blog...