Christophe Pettus: All Your GUCs in a Row: primary_slot_name

Chris van Eijk: A read-only user in PostgreSQL: what it can still do
Chris van Eijk: must be owner of table in PostgreSQL: who may alter it?
How to Deploy #Forem on Rocky Linux #VPS This article provides a guide detailing how to deploy Forem on Rocky Linux ...
Continued 👉 #sidekiq #selfhosted #letsencrypt #rockylinux #rubyonrails #postgresql #selfhosting #forumsoftware #reverseproxy #elasticsearch #rubygems #forum #opensource #redis
Devrim GĂśNDĂśZ: bigquery_fdw works again on every distribution we ship in the RPM repo
VAST Data is looking for: Backend Developer – #Go Expert in #Reykjavik 🇮🇸 #golang #postgresql #azure
Tejaswi Thimmaiah: PostgreSQL Roles and Privileges Explained: A Practical RBAC Guide
pg-java Is The Modern #JDBC Driver For #PostgreSQL-" Developed primarily by #AI with strict human architectural oversight is specifically designed for #Java 21+ and the JVM."
Full details on IProgrammer: dub.sh/AkHzg24
#postgres @planetpostgres.bsky.social
The next Postgres Meetup For All is on November 12th. Join them online for “Postgres Heroics with Logical Replication” with Huseyin Demir!
#PostgreSQL's pgBackRest at PGConf.EU 2026: "The Monday We Learned Who Maintains Our Backups." Tue 20 Oct, 14:45, by David Steele & Jan Wieremjewicz. pgEdge sponsors pgBackRest.
PGX believes in ongoing education and development. We not only encourage our staff to attend conferences and user groups, we also sponsor them!
www.meetup.com/postgresql-1/
Quick reminder: three weeks from Friday I’m at SREday NYC, at Datadog’s office in New York, on November 7.
My talk: Agents Can Write Migrations. They Shouldn’t Ship Them.
#SREday #PostgreSQL #SRE #AIAgents #TigerData
There is strength in numbers! Together we can continue to build a safe community that welcomes everyone! Join PgUS today!
#PostgreSQL 19 RC1 is out, with GA planned for next month. Details: www.postgresql.org/about/news/p...
News: PostgreSQL 19 RC 1 Released!
https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/
EXPLAIN ANALYZE doesn't send rows to the client, and SELECT * was still twice as slow as selecting one column: 64.8 ms vs 32.8 ms on about 100k rows.
The one column came straight from the index. SELECT * had to go to the table: 1,718 buffers instead of 279.
AGLedger used Valkey for queues and load balancing alongside PostgreSQL.
In Part 2 of "When Postgres Is Enough", Michael Cooper explains how pg-boss meant he no longer needed Valkey and what happened during a three-hour simulated agent workload: youtu.be/_rLZQJIqMAs