# PG13 兼容性问题 🔥

**URL:** <https://meta.discourse.org/t/pg13-compatibility-issue/331068>\
**Category:** Bug\
**Created:** [2024年十月15日 22:28 UTC](https://meta.discourse.org/t/pg13-compatibility-issue/331068 "2024-10-15T22:28:32Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted)\
**Post date:** [2024年十月22日 02:29 UTC](https://meta.discourse.org/t/pg13-compatibility-issue/331068/16 "2024-10-22T02:29:05Z")

</div>

感谢 @RGJ 的信息！🙏

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

> <https://github.com/discourse/discourse/pull/29327>
>
> \### 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.

---

_[View the full topic](https://meta.discourse.org/t/pg13-compatibility-issue/331068)._