Update: NetBSD works fine with #postgreSQL18 and the PostGIS extension by adding 18 to the Makefile and compiling/installing the databases/postgresql-postgis2 package.

$ diff Makefile*
44,45c44
< # PGSQL_VERSIONS_ACCEPTED= 17 16 15 14
< PGSQL_VERSIONS_ACCEPTED= 18 17 16 15 14
---
> PGSQL_VERSIONS_ACCEPTED= 17 16 15 14

I should test 14 before filing a fix.

Edit: tested PGSQL 14, filed a problem report, got positive feedback. Bunch of work to add a version number to a Makefile. :)

As the #FreeBSD pkg of the postgis extension is not tied to a database version and the #NetBSD one seems to be, I moved the geo databases to the former. The rest, to NetBSD.
Zabbix, on the other hand, might need to be a little more performant. We'll see.

1204605:20260608:155730.445 slow query: 6.477221 sec, [...]

Plan is to move Zabbix back to the faster machine when #PostgreSQL18 is set.

(15 minutes down time for export, copy, import, restart).

Edit: DB server heat chart. 80 C until done.

Note to self: use pgsql client 18 to list server version 18 databases, as client 16 fails, understandably.

$ psql -U dbuser -d db18 -h host --list
ERROR: column d.daticulocale does not exist
LINE 8: d.daticulocale as "ICU Locale",
^
HINT: Perhaps you meant to reference the column "d.datlocale".

#PostgreSQL18

Started looking at upgrading databases to #PostgreSQL18 on NetBSD and then remembered the PostGIS add-on. Looks like that package (named postgresql-postgis2 though it's v3.6 or so) isn't workable for PGSQL18.

# grep PGSQL_VERSIONS_ACCEPTED Makefile
PGSQL_VERSIONS_ACCEPTED= 17 16 15 14

Next stop: wip (work in progress).

Once again, I tried to pull a zabbix server out of a hat and voila it only supports mysql, so I got a new ports tree and rebuilt from source. I feel like a goldfish sometimes.
Upgrade now supports #PostgreSQL18
Sommaire des formations DALIBO

FORMATION : ajouts de TP, correctifs et revue des cours en intégrant les nouveautés de #PostgreSQL18… les manuels Dalibo viennent d'être mis à jour => https://dali.bo/202605_manuels

Toujours en accès libre sous format html, pdf, ePub, et slides. 👀

Merci à nos collègues #DBA pour leur travail ! 💐

#opensource #SGBD #SQL #formation #PostgreSQL

PostgreSQL 18 saute la case imprimeur.

La 6e édition du livre "PostgreSQL — Architecture et notions avancées" (Guillaume Lelarge & Julien Rouhaud) paraît aujourd'hui en numérique, sur les traces de la version 18.

Pour les irréductibles du papier, la 5e édition (PostgreSQL 16) reste une valeur sûre.

👉 https://dbkr.fr/livre-pg6

#PostgreSQL #OpenSource #DBA #BaseDeDonnées #PostgreSQL18

@dalibo

Des nouveautés de #PostgreSQL18 à la sécurisation des données, en passant par les statistiques et #Kubernetes… 🐘

Les #conférences de la #pgsession18 auront lieu demain à Paris, mais comment y participer à distance ?

Voici le programme **à jour** et les liens utiles : https://dali.bo/202601_pgsession18_distance

#PostgreSQL #SGBD #DBA
#opensource #logicielsLibres

#PostgreSQL 18's new improvements simplify complex workflows, reduce round trips to the database, & make building modern apps more efficient than ever.

Our newest blog is focused on:
→ What's new in RETURNING clause functionality
→ Real-world use cases and performance benefits
→ How to leverage these enhancements in your applications

Perfect for devs & database architects looking to maximize PG18's capabilities.

Check it out: https://www.pgedge.com/blog/postgresql-18-returning-enhancements-a-game-changer-for-modern-applications

#PostgreSQL18 #OpenSource #Postgres

PostgreSQL 18 RETURNING Enhancements: A Game Changer for Modern Applications

PostgreSQL 18 has arrived with some fantastic improvements, and among them, the RETURNING clause enhancements stand out as a feature that every PostgreSQL developer and DBA should be excited about. In this blog, I'll explore these enhancements, with particular focus on the MERGE RETURNING clause enhancement, and demonstrate how they can simplify your application architecture and improve data tracking capabilities.