Planning on attending PGConf NYC 2025? We have a discounted rate with Club Quarters Hotel, Times Square-Midtown! Check it out and book today:

https://2025.pgconf.nyc/venue/

@PostgreSQL #postgres #conference

Postgres FM | Snapshots

Nikolay talks Michael through using cloud snapshots — how they can be used to reduce RTO for huge Postgres setups, also to improve provisioning time, and some major catches to be aware of. Here are some links to things they mentioned:Snapshots on RDS...

*Takes a deep breath*

#MariaDB might be the best general database engine ever and it sucks that the for-profit company using the name kept stepping on rusty rakes over and over again so that people in suits who can't distinguish the corp from the foundation pushed for other platforms.

Side note: #PostgreSQL, I want to love you, but I have so many similar feelings about you as I do about coding in rust. You're too pedantic for your own good.

#database #mysql #postgres

Take a look at “Becoming a PG_STAT_*STAR [Returns]” with Chirag Dave at PGConf NYC 2025!

https://postgresql.us/events/pgconfus2025/sessions/session/2051-becoming-a-pg_stat_star-returns/

@PostgreSQL #postgres #conference

The use of #postgres notify/listen shouldn't be with multiple writers.

Immensely powerful utility, but terrible if you try to do multiple execution in parallel through transactions. 🫠 Although if you use triggers, you can have multi writers, but you lose atomic op.

https://www.recall.ai/blog/postgres-listen-notify-does-not-scale

Postgres LISTEN/NOTIFY does not scale

Postgres LISTEN/NOTIFY can cause severe performance issues under high write concurrency due to a global lock during commit. Learn why it doesn't scale and how to avoid outages.

@patrick I don't know whether this would help in your situation but I've had more success myself in upgrading #postgres in single version increments (so 13 to 14 then 14 to 15).
#Postgres Troubleshooting: Fixing Duplicate Primary Key Rows | Crunchy Data Blog https://www.crunchydata.com/blog/postgres-troubleshooting-fixing-duplicate-primary-key-rows
Postgres Troubleshooting: Fixing Duplicate Primary Key Rows | Crunchy Data Blog

Corrupted unique index? A recent glibc update invalidate a primary key index? Greg has seen a few duplicate primary key issues recently and steps through how to fix these with some special tricks and functions.

Crunchy Data

PgUS is looking for volunteers! We have jobs both large and small so even if you only have a little time to give, we’d love to hear from you!

https://docs.google.com/forms/d/e/1FAIpQLScbgAsSLbvdmx89SsYMDxLM6pkpVNloXmOYWxP9bbdcZBR1vA/viewform

#PostgreSQL #postgres #volunteer

Help us help the community by sponsoring PGConf NYC 2025! Talk to us about sponsorship opportunities today!

https://2025.pgconf.nyc/sponsors/

@PostgreSQL #postgres #conference

In testing a postgres upgrade (13->15) for our mastodon-servcer, I run into a fatal error 'Your installation contains user-defined objects that refer tointernal polymorphic functions with arguments of type "anyarray" or "anyelement". Haven't been able to find a fix for this online, and there seems to be no logfile to pinpoint the cause. Anyone have any suggestions on how to fix this? #techquestion #mastoadmin #postgres
×

It may not be a Broadway show, but we have plenty of entertainment (and elephants)! Get your ticket to PGConf NYC 2025 today!

https://2025.pgconf.nyc/tickets/

@PostgreSQL #postgres #conference