Tomorrow, March 24th, Triangle Postgres Users Group is having their next in-person Meetup! They will be presenting “pgrx, A Modern Framework for Building PostgreSQL Extensions in RUST” with Patrick Reynolds. If you’re local to Raleigh NC, check it out:

https://www.meetup.com/triangle-postgres-users-group/events/313394033/?eventOrigin=network_page

#PostgreSQL #postgres #meetup

We’re delighted to announce Fujitsu as a Gold Sponsor for PgDay Boston!

https://www.postgresql.fastware.com/

#PostgreSQL #postgres #sponsor

Wondering if you should attend PgDay Boston? Look no further than our “About” page for all the reasons why (spoiler alert: you should)!

https://2026.pgdayboston.org/about/

@PostgreSQL #PostgreSQL #postgres

Unable to attend our Meetups? Missed one? Well no worries! Many of them have been recorded and are available on our YouTube channel!

https://www.youtube.com/watch?v=x2M4ulbQ2RY

#speaker #postgres #PostgreSQL #bayareapostgres

Have a PostgreSQL victory or challenge to share with the community? The Pg Summit US call for papers is open until June 1st!

https://2026.postgressummit.us/call-for-papers/

#PostgreSQL #postgres #conference

Using Patroni to Build a Highly Available Postgres Cluster—Part 3: HAProxy

Welcome to Part three of our series for building a High Availability Postgres cluster using Patroni! Part one focused entirely on establishing the DCS using etcd to provide the critical DCS backbone for the cluster, and part two added Patroni and Postgres to the software stack. While it's entirely possible to stop at that point and use the cluster as-is, there's one more piece that will make it far more functional overall.

PgUS is excited to announce the Community Development Committee! We are dedicated to developing participation in the PostgreSQL community through outreach programs and the support of educational endeavors for PostgreSQL users in the United States.

https://postgresql.us/community_development/

#PostgreSQL #postgres #community

Oh fuck #postgres. In 18 they made a change in data path from `/var/lib/postgresql/data` to `/var/lib/postgresql/`.

EDIT:

I was wrong, it's not postgres change, it's change made in "official" docker image, which in fact is not official and maintained by "the PostgreSQL Docker Community". My apologies to pg people.

They "the PostgreSQL Docker Community" (not affiliated with Postgres in any way) did exactly zero checks so users will shoot themselves in a leg in two ways:

  • kinda benign: after 17 → 18 upgrade it won’t start
  • fatal: user mounted docker volume at the old pathContainer restarts and data gone (that’s me)
  • What the actual fuck. Why on earth you couldn’t do a simple fucking check that old directory exists and has data, but new directory is empty, and then start with directory with data spitting warnings that default has been changed and you need to do something about that.

    This is utter incompetence and giving exactly zero fucks about your user base

    We hope you’ll be joining us for PgDay Boston! We have a full day packed with information, networking, and fun! Early Bird tickets are available until April 17th, so get yours today!

    https://2026.pgdayboston.org/registration/

    #PostgreSQL #postgres #conference

    Ctrl-C in psql gives me the heebie-jeebies - Neon

    There are a few different reasons to hit the brakes on a Postgres query. Maybe it’s taking too long to finish. Maybe you realised you forgot to create an index that will make it orders of magnitude quicker. Maybe there’s some reason the results are no longer needed. Or maybe you, or your LLM buddy, […]

    Neon