Re: altering a column's collation leaves an invalid foreign key

Paul A Jungwirth <pj@illuminatedcomputing.com>

From: Paul Jungwirth <pj@illuminatedcomputing.com>

To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-03-25T06:47:26Z

Lists: pgsql-hackers

Attachments

v1-0001-Re-check-foreign-key-if-referenced-collation-was-.patch (text/x-patch) patch v1-0001

On 3/23/24 10:04, Paul Jungwirth wrote:
> Perhaps if the previous collation was nondeterministic we should force a re-check.

Here is a patch implementing this. It was a bit more fuss than I expected, so maybe someone has a 
better way.

We have had nondeterministic collations since v12, so perhaps it is something to back-patch?

Yours,

-- 
Paul              ~{:-)
pj@illuminatedcomputing.com

Commits

Fix error code for referential action RESTRICT
- 086c84b23d99 18.0 landed
doc: Improve description of referential actions
- 1e08905842fb 18.0 landed
Add tests for foreign keys with case-insensitive collations
- 4a2dbfc6be45 18.0 landed
Fix collation handling for foreign keys
- 9321d2fdf808 18.0 landed
Clarify a foreign key error message
- d7a2b5bd8718 18.0 landed