PG13 兼容性问题 🔥

ted · 2024年十月22日 02:29

感谢 @RGJ 的信息！

移除 NULLS NOT DISTINCT OPTION 的 PR 已上线：

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.

話題		回覆	觀看
Restore fails - could not create unique index Self-hosting	21	4169	2020年七月4日
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Self-hosting	7	1321	2022年六月20日
Restore fails: could not create unique index Self-hosting	10	1334	2022年二月13日
Problem with restore Discourse from backup (3.4, quite large DB) Support	17	523	2025年一月14日
Error restoring backup "key is duplicated" Self-hosting	7	1939	2017年八月30日

PG13 兼容性问题 🔥

相關主題