Problème de compatibilité PG13 :feu:

ted · Octobre 22, 2024, 2:29

Merci pour l’info @RGJ !

La PR pour supprimer l’option NULLS NOT DISTINCT est en ligne :

github.com/discourse/discourse

DEV: Remove NULLS NOT DISTINCT from problem check trackers

main ← 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.

Sujet		Réponses	Vues
Restore fails - could not create unique index Installation	22	3836	Juillet 6, 2020
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Installation	8	1188	Juin 20, 2022
Restore fails: could not create unique index Installation	10	1213	Février 13, 2022
Problem with restore Discourse from backup (3.4, quite large DB) Support	18	235	Janvier 14, 2025
Error restoring backup "key is duplicated" Installation	8	1806	Août 31, 2017

Problème de compatibilité PG13 :feu:

Sujets connexes