PostGIS BRIN support keep or remove?

As noted in PostGIS chat channels and on Mapstodon.space

We found a serious bug with BRIN on PostGIS geometries which leaves us with two options

  • Spend time fixing it
  • Remove BRIN Support
0 voters

Voice your opinion on which you’d prefer. I’d personally prefer to remove the support. Detailed discussion about it here - A number of BRIN opclasses seems to broken / missing the MERGE procedure

We decided to keep it and with upgrade logic. Seemed there were more people using it than we thought.

Discussed here - The postgis-devel January 2025 Archive by thread

Currently in the master and stable-3.5.
Would love if some folks using it would test it out.

More details here - PostGIS BRIN upgrade