Проблема совместимости PG13 🔥

ted · 22.Октябрь.2024 02:29:05

Спасибо за информацию @RGJ!

PR по удалению NULLS NOT DISTINCT OPTION уже создан:

github.com/discourse/discourse

DEV: Remove NULLS NOT DISTINCT from problem check trackers (#29327)

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

merged 02:47AM - 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.

Тема		Ответов	Просм.
Restore fails - could not create unique index Self-hosting	22	3994	06.07.2020
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Self-hosting	8	1248	20.06.2022
Restore fails: could not create unique index Self-hosting	10	1268	13.02.2022
Problem with restore Discourse from backup (3.4, quite large DB) Support	18	325	14.01.2025
Error restoring backup "key is duplicated" Self-hosting	8	1864	31.08.2017

Проблема совместимости PG13 🔥

Связанные темы