We've posted a video of Palak Chaturvedi's talk Debugging Data Corruption in PostgreSQL https://youtu.be/82SFq5SlCx0 #postgresql #PGConfdev
We've posted a video of Palak Chaturvedi's talk Debugging Data Corruption in PostgreSQL https://youtu.be/82SFq5SlCx0 #postgresql #PGConfdev
Tengo instalaciones de #ejabberd por @ejabberd y #prosody por @prosodyim. Ambos facil de instalar (paquetes de #Debian) y mantener, con muy poco mantenimiento.
La configuración de ejabberd (YAML) me gusta mas que prosody (Lua). Uso ejabberd con #PostgreSQL, prosody con "file storage".
Prosody ya tiene invitaciones, que me parece buenisimo:
https://blog.prosody.im/great-invitations/
No tengo experiencia con otros servidores, como #Tigase por @tigase u #Openfire por @news.
And why does `substr()` in #PostgreSQL treat `1` as the first character, instead of `0`, LIKE EVERYTHING ELSE?!
Postgres is Too Good (And Why That's Actually a Problem)
https://dev.to/shayy/postgres-is-too-good-and-why-thats-actually-a-problem-4imc
Using #gotosocial + #postgresql for a small instance (25 to 50 users) on a small server (intel N2800/4Gb/SSD). A good idea? Any feedbacks?
A new blog post: query @MongoDB from @duckdb using #PostgreSQL extensions
Nouvel article de blog, en anglais dans le texte :
"From database burden to cloud efficiency: Sonar's journey to faster processing & lower costs"
https://www.sonarsource.com/blog/sonars-journey-to-faster-processing-lower-costs/
Message de service : notre instance #mobilizon est en maintenance depuis 3 jours.
Contexte : suite à la dernière mise à jour mineure, on a découvert que la version minimum de #PostgreSQL est passée de 11 à 13. On doit donc mettre à jour notre cluster PGSQL pour régler le problème.
So, it finally happened: #PostgreSQL added two features that conflict with each other. I suppose it had to despite all the checks.
The two features are parallel index build and pg_stat_progress_create_index. Normally, the progress table lets you check build so that you know how much there is to go and whether to abort or not.
The conflict? Parallel index build with 6+ workers is so fast that there's no time to check the progress table before it's done. Even on a 50GB table.
Don't miss Charles Feddersen's keynote at #PosetteConf Livestream 1 discussing what Microsoft is building for #Postgres in 2025.
Today is the day! The wait is over. Grab a cup of tea or an espresso and join the #PosetteConf livestream at 8am PT to hear from #Postgres experts, users, and enthusiasts. You won't be disappointed.
Check out the full schedule: https://posetteconf.com/2025/schedule/
@RichiH Does this grow #PostgreSQL databases? ;-)
The #Docker container for #PostgreSQL 18 beta 1 is available.
That's a good time to start with tests.
https://hub.docker.com/_/postgres/
This 4th year of the virtual @posetteconf will have:
45 a-ma-zing speakers from 21 companies
4 livestreams
42 #PostgreSQL talks
Live virtual hallway track on Discord
The 2 keynotes are by brilliant speakers Bruce Momjian & Charles Feddersen
+ 18 talks about the Postgres core
+ 12 Postgres ecosystem talks
+ 10 talks about Azure Database for PostgreSQL
Hope to see you—or your Postgres database friends—at #PosetteConf
/End (4)
Now everything is distributed. Including how we connect with each other: email, discord, telegram, slack, teams, linkedin, mastodon, youtube, reddit...
Another way? Traveling by planes , trains
, or automobiles
to in-person #PostgreSQL conferences. I've never been to a bad Postgres conference, they've all been pretty magical.
But not everyone can travel: kids, budgets, caregiving, life
That's one of the reasons my team at Microsoft created #PosetteConf. To make great #PostgreSQL content accessible to anyone w/ laptop + internet
So what's in store for @posetteconf this year? This "ultimate guide" blog post gives you categories & tags to help figure out what's relevant for you(3): https://techcommunity.microsoft.com/blog/adforpostgresql/ultimate-guide-to-posette-an-event-for-postgres-2025-edition/4419896
When I was an engineer in the developer tools group at Sun, our team was co-located. We coded together, ate lunch together, played volleyball together—& sometimes even juggled in the halls, waiting for servers to reboot (crazy that I still remember the server's names: skippy, jif, and peterpan)
Today, the #PostgreSQL community I work with is spread across time zones, countries, & companies
(2)
This week on Tue/Wed/Thu Jun 10-12 is @posetteconf, a free & virtual developer conference with 4 livestreams, 42 talks about Postgres, & a live hallway track on Discord
If you use #PostgreSQL there's probably something here for you: https://posetteconf.com/2025/schedule/
(1) A quick story on why #PosetteConf matters (and why virtual conferences matter)
We've posted a video of Sam Willis's talk Compiling Postgres to WASM with PGlite (PGConf.dev 2025) https://youtu.be/hlWWG5WZHOA
#postgresql #PGConfdev
Deepintodev.com reviews how modern database storage engines store, retrieve, and update database table rows on memory and disk. This serves as a foundation to understanding how indexes and clustered indexes work, the concerned data structures, and their use cases; these are reviewed as well.
"How Databases Store Your Tables on Disk"
https://www.deepintodev.com/blog/how-databases-store-your-tables-on-disk
In just
days you'll get your chance to grab some extra cool #PosetteConf swag!