PG13 互換性不具合

ted · 2024 年 10 月 22 日午前 2:29

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.

トピック		返信	表示
Restore fails - could not create unique index Installation	22	3786	2020 年 7 月 6 日
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Installation	8	1170	2022 年 6 月 20 日
Restore fails: could not create unique index Installation	10	1197	2022 年 2 月 13 日
Problem with restore Discourse from backup (3.4, quite large DB) Support	18	212	2025 年 1 月 14 日
Error restoring backup "key is duplicated" Installation	8	1802	2017 年 8 月 31 日

PG13 互換性不具合

関連トピック