Fun fact, #PostgreSQL limits identifiers to 63 bytes. This is reasonable.

But it will accept creation of resources with identifiers longer than that and automatically truncate them with nothing more than a notice-level log message.

I sincerly hope the SQL standard mandates this because if not, it is a puzzling, bug-inducing choice.

Come see Vik Fearing (@xocolatl) talk about "Window Functions Are Easier and More Powerful Than You Think" at Nordic PGDay in Copenhagen!

#postgresql #conference #copenhagen

https://www.postgresql.eu/events/nordicpgday2025/sessions/session/6042-window-functions-are-easier-and-more-powerful-than-you-think/

Come see Ellyne Phneah talk about "Tuning community parameters: Hosting PostgreSQL events that perform"!

#pgDayParis #PostgreSQL #conference #pgeu

https://www.postgresql.eu/events/pgdayparis2025/sessions/session/6334-tuning-community-parameters-hosting-postgresql-events-that-perform/

 In case you missed the info on other platforms, we're gonna have a #PostgreSQL #meetup in Paris next month on Thursday 13th March (the week before @pgDayParis) and I'll be there speaking about incremental backups (and a little bit about #pgBackRest 🤫)

https://www.meetup.com/postgresql-user-group-paris/events/305774177

This post I wrote on Postgres transaction isolation is still my go-to cheat sheet. If you need to check what isolation level to use for xyz, it might help you too :)

https://jflessau.com/dev/postgres-transaction-isolation-levels/

#postgres