If you're running Debian 12 and Postgres, you're in or around the Americas, and you're planning on upgrading to Debian 13, you might hit a fun little snag [..]

https://rachelbythebay.com/w/2025/09/11/debtz/

Debian 13, Postgres, and the US time zones

Link: https://rachelbythebay.com/w/2025/09/11/debtz/
Discussion: https://news.ycombinator.com/item?id=45218111

Another blog post has been drafted on a totally new topic for me: database schema migrations with Atlas. Maybe if I keep this up and find enough topics, I can start to get on a regular cadence?! That would be nice. Fortunately Medium lets me schedule posts.

The goal for my blog is not only to demo what I'm working on, but also write the blog posts I wish I had for particular topics. A how-to should be a short version of what's in the docs since often times tools can do many things, but a blog post is much shorter and to-the-point.

Supabase OrioleDB Patent: now freely available to the Postgres community

Link: https://supabase.com/blog/orioledb-patent-free
Discussion: https://news.ycombinator.com/item?id=45196173

Did you know having a shell inside a #postgres #container anyone can log in your database without a password? At least when using the official #docker image.

All access is set to 'trust' in 'pg_hba.conf'. This can be changed and set to another value to enforce authentication from inside the docker container as well.

Somone else already wrote an article about hardening the setup: https://pankajconnect.medium.com/container-security-tips-for-securing-postgresql-instances-in-docker-9de5d2a932fb

(There are for sure more articles of that sort to find.)

Richard van der Hoff, a member of the team that runs the https://Matrix.org homeserver, has written a detailed blog post about diagnosing and fixing a problem where #Matrix rooms would simply stop working

How we discovered, and recovered from, #Postgres corruption on the https://matrix.org homeserver https://matrix.org/blog/2025/07/postgres-corruption-postmortem/

I really enjoyed learning something by reading #documentation today.

> SELECT * FROM a JOIN b USING (id);

as a shorthand for

> SELECT * FROM a JOIN b WHERE a.id=b.id;

It's one of the perks of getting older, isn't it?

I'm a Senior #Software Engineer with 20+ years of professional experience.

I'm based in the USA and looking for #remote work.

I have primarily worked with web technologies such as #JavaScript, #HTML, #CSS, #nodejs, and #typescript.

My last job was as a Senior #React Engineer.

I've worked with #Postgres, #MySQL, and #MSSQL databases.

Backend tech includes C#, Go, PHP, and ASP.

Countless projects ranging from SPAs to $100 million ecommerce sites to enterprise level software.

Microsoft's MongoDB-compatible DocumentDB, based on Postgres, is gaining traction! The project is joining the Linux Foundation with AWS on board.

https://opensource.microsoft.com/blog/2025/08/25/documentdb-joins-the-linux-foundation/
https://aws.amazon.com/blogs/opensource/aws-joins-the-documentdb-project-to-build-interoperable-open-source-document-database-technology/

ICh verwende paperless schon so lange, dass meine postgres im docker bei version 13 ist. gerade gemerkt, dass paperless-ngx ab 2.18 aber minimum 14 braucht. also nächste woche mal das projekt "DB auf aktuellen Stand bringen". wird lustig. ich ahne es schon.

#paperless-ngx #postgres

Watch this space on Monday, 1 September for the full PGConf.EU program!
Packed with world-class PostgreSQL talks and community sessions — this is an event you won’t want to miss.
In Riga, Latvia on 21-24 October 2025
#pgconfeu #postgresql #postgres #conference #opensource

SQL dumps created with current releases of "pg_dump" (namely 17.6, 16.10, 15.14, 14.19 or 13.22) can no longer be loaded with earlier versions of "psql" because they contain new "\restrict" commands that did not exist in earlier versions and will cause "invalid command" errors. The reason for this change is CVE-2025-8714. Strange to see breaking changes in a project like #Postgres #PostgreSQL

Kommentar: #Microsoft schickt #DocumentDB zum Schutz zur #LinuxFoundation | Developer https://www.heise.de/meinung/Kommentar-Microsofts-DocumentDB-sucht-Schutz-bei-der-Linux-Foundation-10620986.html #SQL #MongoDB #Mongo #Postgres #PostgreSQL #NoSQL @linuxfoundation

#Microsoft Open-sourced their #DocumentDB as an MIT-licensed project.

Wire-compatible with #MongoDB, built on top of #PostgreSQL.

The project now is included into #Linux Foundation.

I do think this is a disruptor, especially when viewing MongoDB's licensing schemes. It builds on all the maturity that is PostgreSQL.

https://github.com/documentdb/documentdb

Invincible #Postgres Saga, episode 3...

(At least this didn't happen on production )

Earlier this week I tried to do some tests on my "wonderful" misconfigured testing environment. I had some errors here and there and they had to reveal themselves during my experiment...
To make everthing up-to-date I had to refresh data in my app, which uses #Patroni #Postgresql database. Of course it crashed when I tried to do it. It didn't turn down whole cluster, only that one server, and in theory it still had normal API access. I expected it to come back quickly after I fixed things breaking my servers. But for some reason it couldn't. It didn't even try, at least in any visible way.
Seriuosly it was the most disturbing thing there It should try to do something, right?!?
I tried to restart services in panic, without any result. It was late and I finished work for that day. Tired and worried I had to leave it stuck in "cannot reach consistent state" stage.

Next day I thought about doing force reinit or something to move it. But when I log into that server... Everything just worked
I checked logs... Almost nothing special, just like database was stuck and after ~14 hours suddenly started working. Only one line telling backup was restored.
Damn, what backup?!? Why I don't understand what it did?!? And why it needed so much time?!?

At least I had working environment and didn't had to wonder what to do. Maybe my first chaotic attempts to force it to work did more harm than good and I should just leave it...

Someone should write in docs, which API status means "just leave me alone, trying to fix things" It would be easier.

Found out about #redka recently. A #redis implementation using #sqlite or #postgres.

I've adapted to using embedded cache libraries. Until redis is a must. This may make that embed cache less necessary when using #golang.

https://github.com/nalgeon/redka

We want all voices to be heard in our community and the PgUS Diversity Committee is hard at work ensuring that happens!

https://postgresql.us/diversity/