MobilityDB Files

This is a bugfix release for 1.3. Every installation running PostgreSQL 18.7, or the minor releases issued with it, needs it: on those servers CREATE EXTENSION mobilitydb fails with MobilityDB 1.3.1 and earlier.

PostgreSQL 18.7 compatibility

PostgreSQL 18.7 refuses an operator whose commutator returns another data type. MobilityDB 1.3.1 declares the intersection of a date span set and a date, datespanset * date and span_intersection(datespanset, date), as returning a date, while its commutator date * datespanset returns a datespanset, so creating the extension stops with:

ERROR:  commutator operator * does not return the same data type as operator *

MobilityDB 1.3.2 declares it as returning a datespanset, which is also the value it computes: with 1.3.1, on any PostgreSQL version, datespanset * date reads the span set it computes as a date.

Credit: Christoph Berg, who reported the issue for the Debian packages.

Upgrading

Compile and install MobilityDB 1.3.2, then run in each database:

:::sql
ALTER EXTENSION mobilitydb UPDATE TO '1.3.2';

The upgrade drops the operator * (datespanset, date) and its function span_intersection(datespanset, date) and creates them again with the datespanset result type; nothing else in the catalog changes. A database created at 1.3.1 keeps working once PostgreSQL is updated to 18.7, and the update runs before or after it. Update it before taking a dump to restore on PostgreSQL 18.7, since a restore creates the extension again.

What's Changed

• Build stable-1.3 on the current GitHub runner images by @estebanzimanyi in https://github.com/MobilityDB/MobilityDB/pull/3573
• Bump stable-1.3 to 1.3.2 with its upgrade file from 1.3.1 by @estebanzimanyi in https://github.com/MobilityDB/MobilityDB/pull/3571

Full Changelog: https://github.com/MobilityDB/MobilityDB/compare/v1.3.1...v1.3.2