pgconfnycHelp our community keep up to date with the latest PostgreSQL news and education! Talk to us about sponsorship opportunities today!
https://2025.pgconf.nyc/sponsors/
@PostgreSQL #postgres #conference
Learn all about “Best practices for Ephemeral Environments with PII for Postgres” with Monica Sarbu at PGConf NYC 2025!
@PostgreSQL #postgres #conference
Come on click on the link…we’ve been waiting for you…where the tickets are hers and theirs and his for PGConf NYC!
https://2025.pgconf.nyc/tickets/
@PostgreSQL #postgres #conference
Michal 
I was not very satisfied with the idea of running a separate #postgres instance for #immich (especially since I already have one running on the host), but with the recent migration to vectorchord I was kind of forced to (tried to install a bunch of .debs, left a mess that would fail to start, ran out of FAFO time).
It turns out that there was nothing to be afraid of, the Postgres container only uses 60MB of RAM and is sitting mostly idle.
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
Douglas J Hunley
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...
Scott Williams 🐧*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.
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
Alejandro BaezThe 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
MikeZ