PG13 compatibility issue 🔥

ted · October 22, 2024, 2:29am

Thanks for the info @RGJ!

The PR for removing the NULLS NOT DISTINCT OPTION is up:

github.com/discourse/discourse

DEV: Remove NULLS NOT DISTINCT from problem check trackers

discourse:main ← discourse:dev/remove-nulls-not-distinct-from-problem-check-trackers

opened 02:28AM - 22 Oct 24 UTC

Drenmi

+12 -0

### What is this change? We added `NULLS NOT DISTINCT` to a unique index on `…problem_check_trackers`. This option is only available in PG15+. It does not in itself break PG13, but restoring a PG15+ backup to PG13 currently errors out. It seems this is an operation that's more common than we first thought. This commit fixes that by removing the `NULLS NOT DISTINCT`. ### Don't we need it, since we added it? We already have another, backwards-compatible approach to do the same thing in place, so this shouldn't change existing behaviour.

Topic		Replies	Views
Backup failed due to PG/SQL errors Installation	9	2196	December 17, 2020
Import failing with `could not create unique index` Installation	6	2654	July 13, 2020
Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore Installation	7	1616	April 25, 2023
Corrupt indexes in PG12, how do I fix? Installation	44	10789	January 26, 2023
Forum offline due to failed rebuilds on Tests-Pass Installation	1	893	December 11, 2020

PG13 compatibility issue 🔥

Related Topics