Hive AI is hiring Senior Software Engineer - Backend
#node #api #rest #postgresql #seniorengineer
San Francisco, California
Full-time
Hive AI
Job details https://jobsfordevelopers.com/jobs/senior-software-engineer-backend-at-thehive-ai-nov-23-2021-a6c833?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
#SQL best practices – don’t compare count(*) with 0 #postgresql – select * from depesz; https://www.depesz.com/2024/12/01/sql-best-practices-dont-compare-count-with-0/
EspritsCollaboratifs, la boite où je bosse, recrute une ou un adminSys en CDI, à Fontenay-sous-Bois dans l'est parisien, ou en télétravail : https://www.curebot.fr/recrutements/#jobs
It's official - we are now a community-recognized NPO by the PostgreSQL Global Development Group!
What does this mean? 
We support the open source #PostgreSQL RDBMS as our primary mission, and manage our organization in accordance with the official PGDG Nonprofit Organizations policy. Learn more here:
On June 12, join our CEO @c2main at 11:30 AM CEST for a FREE livestream @ @posetteconf regarding Pressure Stall Information within the world of #PostgreSQL.
Use this link to add the livestream to your calendar & optionally register, or follow us to get the recording after the conference when it becomes available!
posetteconf.com/2025/talks/resource-control-admission-i-have-a-date-with-my-psi/
Implementing SQL JOIN Support in ChronDB via PostgreSQL Protocol
The game of creating databases using #git internals continues
this week was the time to implement inner/left/right join in the #postgresql protocol
I tried to explain a little about the architecture implemented to perform joins
https://www.moclojer.com/blog/implementing-sql-join-support-in-chrondb-via-postgresql-protocol/
L'estructura tècnica d'#appy funciona gràcies a Python, fastAPI, #Postgresql (base de dades) i #Redis (memòria cau).
Tot de manera asincrona per evitar punts de bloqueig, passen moltes coses en parall·lel, simultàniament, bàsic per a tenir fluïdesa tant en les interaccions amb altres servidors com amb les aplicacions client.
appy funciona bé fins i tot en una #Raspberry 4B, per tant també és una opció vàlida per a tenir el perfil fediversal auto gestionat i a casa.
Play Wordle in Your PostgreSQL Database: A SQL Implementation
Imagine playing the popular Wordle game directly from your PostgreSQL database! This innovative implementation not only showcases SQL's capabilities but also offers a fun way to engage with database q...
https://news.lavx.hu/article/play-wordle-in-your-postgresql-database-a-sql-implementation
We're happy to see our own Frédéric has been interviewed as a #PostgresFriend! See his interview with @ascherbaum on #PostgreSQLLife:
Esta es la lista con los capítulos del tutorial de #PostgreSQL y el lenguaje #SQL:
https://www.youtube.com/watch?v=8_HFyjcUt6Q&list=PLtdeXn2f7ZbNOTrW0POHNuoNbgpc-Qo-6.
Suscríbete a mi canal.
#bbdd #SiguemeYTeSigo #Followback
Nota: imagen generada con IA generativa.
PostgreSQL Full-Text Search: Fast When Done Right (Debunking the Slow Myth)
Link: https://blog.vectorchord.ai/postgresql-full-text-search-fast-when-done-right-debunking-the-slow-myth
Discussion: https://news.ycombinator.com/item?id=43627646
Unlocking PostgreSQL's Full-Text Search Potential: The 50x Speedup Revelation
Recent insights reveal that PostgreSQL's built-in full-text search (FTS) can achieve remarkable performance improvements—up to 50 times faster—when optimized correctly. By addressing common pitfalls i...
Revolutionizing SQL with EdgeQL: Gel and Drizzle's Game-Changing Partnership
The collaboration between Gel and Drizzle is set to redefine SQL workflows for developers. By integrating Drizzle's SQL-centric approach with Gel's powerful EdgeQL, this partnership promises enhanced ...
My hot take: if you chose MySQL in 2025, you are doing it wrong. Just Use Postgres™
Some time ago I mentioned here, in half-joking way, self-fixing software I work with. I said Patroni #Postgres has the best regeneration ability I've ever seen. And currently "the best ability" includes:
> After network migrations servers changed IP addresses. It broke etcd config so I had to completely delete that config and initialize etcd cluster again. Which also forced cleaning and renewing Patroni config because it is strongly dependent on etcd. Even when configuration temporarily didn't exist, connection with WAL archives (technically other separate server) wasn't interrupted (I am not even sure if real data transfer could happen at that time). It was seemingly enough to start new #database cluster from last timeline. I don't know WHAT forced servers to immediately pull that data on fresh start. At migration time there weren't any real production data so I didn't even purposely try to restore anything.
> Not so long time later (and now with real production things) some script tests, causing lots of database changes in relatively short time, beyond former server's capacity, killed master server. Patroni switched as intended and I could work on increasing server's capacity (had to do it live, not very convenient). First server finally decided data corruption was too big and to fix it automatically deleted whole /var/lib/postgresql/* directory and started to recreate thing from scratch, using data from new master server (and was doing it with at least 2 GB/s speed because why not? 
).
> During above mentioned process impatient tester hit again with their not optimised scripts, finally killing whole cluster. Swearing silently I increased remaining servers as it was only thing I really could do. Postgresql API mostly wasn't responsive, it had limited info about last state before final failure. It wasn't possible to force any change or affect it in any way.
First server decided to delete whole directory again and recreate it (at least this time I saw exact moment in logs), at the same time second server did rewind to state of third server (why??). All these things happened automatically, without my help. I wouldn't even know what to do 
And it's only beginning when we use it on production. Now I wait for stubborn users to do some more unintended durability tests... Maybe I would see it's even more invincible 
New episode of #TalkingPostgres #podcast 
Bruce Momjian, #PostgreSQL core team member, joined me on Ep26 to talk about open source leadership—with rabbitholes on servant leadership, the art of public speaking, the power of gratitude, & bow ties
Boosts appreciated 
to help more people discover the podcast
https://talkingpostgres.com/episodes/open-source-leadership-with-bruce-momjian
Hello, hachyderm! we've been working hard on building up our ansible runbooks and improving hachyderm's overall resilience. Recently, we've been focusing on is database resilience.
We're getting close to retiring our original database server (finally!) and preparing to move to a fully ansible-managed set of databases servers, primary and replica on new hardware. We'll send another announcement when we do the cut over. The team has done excellent work to make this highly automated, quick, and painless! 
Done:
author ansible roles for managing postgresql, pgbackrest (backups), pgbouncer, and primary/replica failover decide to continue with pgbouncer and *not* use pgcat rotate database passwords order new replica database hardware order new future primary database hardware
To do soon:
rebuild replica database with ansible scripts prepare primary database with ansible scripts start replicating to new database replica cut over to new database server 
We're also planning on open-sourcing our ansible roles in the coming weeks - just a little housekeeping & tidying up before we do!
