PG13 兼容性问题 🔥

ted · 2024 年10 月 18 日 04:35

我在这里有一个 PR，应该也能用于 PG13。

github.com/discourse/discourse

FIX: Make problem check tracker unique constraint work on PG13

main ← fix/problem-check-target-pg13

opened 03:40AM - 18 Oct 24 UTC

Drenmi

+32 -11

### What is this change? In #29169 we added a `NULLS NOT DISTINCT` option to …the unique index on `problem_check_trackers`. This is to enforce uniqueness even when the `target` is `NULL`. (Postgres considers all `NULL`s to be distinct by default.) However, this only works in PG15. In PG13 it does nothing. This commit adds a default dummy string value `__NULL__` to `target`. Since it's a string, PG13 will be able to correctly identify duplicate records. ### Is it safe to run this? Adding a default value will lock the table and can cause issues on large tables, but the `problem_check_trackers` table is constrained by the number of problem check classes, and is in the ballpark of 10-100 rows.

我们仍在考虑这种情况在实际中有多大可能性，以及我们应该在多大程度上投入精力来规避它。

话题		回复	浏览量
Restore fails - could not create unique index Installation	22	3834	2020 年7 月 6 日
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Installation	8	1187	2022 年6 月 20 日
Restore fails: could not create unique index Installation	10	1213	2022 年2 月 13 日
Problem with restore Discourse from backup (3.4, quite large DB) Support	18	234	2025 年1 月 14 日
Error restoring backup "key is duplicated" Installation	8	1806	2017 年8 月 31 日

PG13 兼容性问题 🔥

相关话题