PG13 호환성 문제 🔥

ted · 10월 22, 2024, 2:29오전

@RGJ! 정보 감사합니다

NULLS NOT DISTINCT OPTION을 제거하는 PR이 올라갔습니다:

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

PG13 호환성 문제 🔥

Related topics