PG13 호환성 문제 🔥

ted · 10월 18, 2024, 4:35오전

PG13에서도 작동할 것으로 보이는 PR을 올렸습니다.

github.com/discourse/discourse

FIX: Make problem check tracker unique constraint work on PG13 (#29272)

main ← fix/problem-check-target-pg13

merged 02:45AM - 21 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 Self-hosting	21	4205	7월 4, 2020
"EXCEPTION: psql failed: DETAIL: Key (post_id)=(36946) is duplicated." Self-hosting	7	1337	6월 20, 2022
Restore fails: could not create unique index Self-hosting	10	1351	2월 13, 2022
Problem with restore Discourse from backup (3.4, quite large DB) Product Support	17	567	1월 14, 2025
Error restoring backup "key is duplicated" Self-hosting	7	1971	8월 30, 2017

PG13 호환성 문제 🔥

Related topics