eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

212
active users

#postgresql

10 posts10 participants1 post today
Replied in thread

@carloshr @tecnologia

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:

blog.prosody.im/great-invitati

No tengo experiencia con otros servidores, como #Tigase por @tigase u #Openfire por @news.

blog.prosody.im · Great Invitations
More from Prosody IM

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.

Replied in thread

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)

👉 posetteconf.com/2025/schedule/

POSETTESchedule | POSETTE: An Event for Postgres 2025Schedule and Sessions for POSETTE: An Event for Postgres, a virtual and free developer event happening Jun 10-12, 2025. There will be 4 separate livestreams. Organized by the Postgres team at Microsoft.
Replied in thread

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): techcommunity.microsoft.com/bl

TECHCOMMUNITY.MICROSOFT.COMUltimate Guide to POSETTE: An Event for Postgres, 2025 edition | Microsoft Community HubA guide to help you navigate all 42 talks at the 4th annual POSETTE: An Event for Postgres, a free and virtual developer event happening Jun 10-12, 2025.
Continued thread

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: posetteconf.com/2025/schedule/

🧵(1) A quick story on why #PosetteConf matters (and why virtual conferences matter) 👇

POSETTESchedule | POSETTE: An Event for Postgres 2025Schedule and Sessions for POSETTE: An Event for Postgres, a virtual and free developer event happening Jun 10-12, 2025. There will be 4 separate livestreams. Organized by the Postgres team at Microsoft.

Test Postgres in Python Like SQLite : A #Python testing library that provides seamless integration between PGlite and Python test suites. Get the full power of PostgreSQL in your tests without the overhead of a full PostgreSQL installation.

github.com/wey-gu/py-pglite

PGlite wrapper in Python for testing. Test your app with Postgres just as lite as SQLite. - wey-gu/py-pglite
GitHubGitHub - wey-gu/py-pglite: PGlite wrapper in Python for testing. Test your app with Postgres just as lite as SQLite.PGlite wrapper in Python for testing. Test your app with Postgres just as lite as SQLite. - wey-gu/py-pglite

A great way to spend an afternoon is watching past #tech talks at conferences... no? 📽️

Well, if it's interesting enough to you, maybe take a look at "Stats roll, baby, stats roll" from Cédric Villemain, presented at #FOSDEM2025. Here, he discusses using the PACS (#PostgreSQL Advanced Cumulative Statistics) extension to explore what is offered by #Postgres as well as how to define your own new kind of statistics.

mirrors.dotsrc.org/fosdem/2025

#PostgreSQL performance has improved exponentially since PG15, with critical changes such as basic support for logical replication to seamless failover slots, only being able to set basic thresholds for autovacuum vs. being adaptive, and limited parallel query support evolving to expanded parallel aggregates.

Get advanced performance tuning techniques for PG17 as well as details on what's changed since PG15 in this blog from Ibrar Ahmed:

pgedge.com/blog/postgresql-per

www.pgedge.compgEdgeFully distributed PostgreSQL

I wrote a thing about a somewhat bizarre CPU behavior observed during #PostgreSQL benchmarks on large systems. Seems related to cores being too idle, but hard to "prove" these internal CPU behaviors :-( Also, not sure how to mitigate it.

vondra.me/posts/benchmarking-i

Tomas Vondra · Benchmarking is hard, sometimes ...Benchmarking complex systems can be difficult. Here's a problem I'm currently investigating, possibly related to process scheduling.