pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fix broken-FK-detection query in release notes 5+ messages / 1 participants [nested] [flat]
* pgsql: Fix broken-FK-detection query in release notes @ 2025-05-30 14:22 Álvaro Herrera <alvherre@kurilemu.de> 0 siblings, 0 replies; 5+ messages in thread From: Álvaro Herrera @ 2025-05-30 14:22 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix broken-FK-detection query in release notes Commits 53af9491a043 and 2d5fe514052a fixed a number of problems with foreign keys that reference partitioned tables, and a query to detect already broken FKs was supplied with the release notes for 17.1, 16.5, 15.9, 14.14, 13.17. However, that query has a bug that causes it to wrongly report self-referential foreign keys even when they are correct, so if the user was to drop and rebuild the FKs as indicated, the query would continue to report them as needing to be repaired. Here we fix the query to not have that problem. Reported-by: Paul Foerster <paul.foerster@gmail.com> Discussion: https://postgr.es/m/5456A1D0-CD47-4315-9C65-71B27E7A2906@gmail.com Backpatch-through: 13-17 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3e75313c2beaf1905bc47623902e0983fb731f8a Modified Files -------------- doc/src/sgml/release-13.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix broken-FK-detection query in release notes @ 2025-05-30 14:22 Álvaro Herrera <alvherre@kurilemu.de> 0 siblings, 0 replies; 5+ messages in thread From: Álvaro Herrera @ 2025-05-30 14:22 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix broken-FK-detection query in release notes Commits 53af9491a043 and 2d5fe514052a fixed a number of problems with foreign keys that reference partitioned tables, and a query to detect already broken FKs was supplied with the release notes for 17.1, 16.5, 15.9, 14.14, 13.17. However, that query has a bug that causes it to wrongly report self-referential foreign keys even when they are correct, so if the user was to drop and rebuild the FKs as indicated, the query would continue to report them as needing to be repaired. Here we fix the query to not have that problem. Reported-by: Paul Foerster <paul.foerster@gmail.com> Discussion: https://postgr.es/m/5456A1D0-CD47-4315-9C65-71B27E7A2906@gmail.com Backpatch-through: 13-17 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4620cd9c1c80984419ff135bfc1a9c79ff16ab6f Modified Files -------------- doc/src/sgml/release-15.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix broken-FK-detection query in release notes @ 2025-05-30 14:22 Álvaro Herrera <alvherre@kurilemu.de> 0 siblings, 0 replies; 5+ messages in thread From: Álvaro Herrera @ 2025-05-30 14:22 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix broken-FK-detection query in release notes Commits 53af9491a043 and 2d5fe514052a fixed a number of problems with foreign keys that reference partitioned tables, and a query to detect already broken FKs was supplied with the release notes for 17.1, 16.5, 15.9, 14.14, 13.17. However, that query has a bug that causes it to wrongly report self-referential foreign keys even when they are correct, so if the user was to drop and rebuild the FKs as indicated, the query would continue to report them as needing to be repaired. Here we fix the query to not have that problem. Reported-by: Paul Foerster <paul.foerster@gmail.com> Discussion: https://postgr.es/m/5456A1D0-CD47-4315-9C65-71B27E7A2906@gmail.com Backpatch-through: 13-17 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/50a8959cd50bb346b2479ac66bb4f0f474409c51 Modified Files -------------- doc/src/sgml/release-17.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix broken-FK-detection query in release notes @ 2025-05-30 14:22 Álvaro Herrera <alvherre@kurilemu.de> 0 siblings, 0 replies; 5+ messages in thread From: Álvaro Herrera @ 2025-05-30 14:22 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix broken-FK-detection query in release notes Commits 53af9491a043 and 2d5fe514052a fixed a number of problems with foreign keys that reference partitioned tables, and a query to detect already broken FKs was supplied with the release notes for 17.1, 16.5, 15.9, 14.14, 13.17. However, that query has a bug that causes it to wrongly report self-referential foreign keys even when they are correct, so if the user was to drop and rebuild the FKs as indicated, the query would continue to report them as needing to be repaired. Here we fix the query to not have that problem. Reported-by: Paul Foerster <paul.foerster@gmail.com> Discussion: https://postgr.es/m/5456A1D0-CD47-4315-9C65-71B27E7A2906@gmail.com Backpatch-through: 13-17 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/db54be898a68b8abccf1d5759dcbde9e23c56195 Modified Files -------------- doc/src/sgml/release-16.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix broken-FK-detection query in release notes @ 2025-05-30 14:22 Álvaro Herrera <alvherre@kurilemu.de> 0 siblings, 0 replies; 5+ messages in thread From: Álvaro Herrera @ 2025-05-30 14:22 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix broken-FK-detection query in release notes Commits 53af9491a043 and 2d5fe514052a fixed a number of problems with foreign keys that reference partitioned tables, and a query to detect already broken FKs was supplied with the release notes for 17.1, 16.5, 15.9, 14.14, 13.17. However, that query has a bug that causes it to wrongly report self-referential foreign keys even when they are correct, so if the user was to drop and rebuild the FKs as indicated, the query would continue to report them as needing to be repaired. Here we fix the query to not have that problem. Reported-by: Paul Foerster <paul.foerster@gmail.com> Discussion: https://postgr.es/m/5456A1D0-CD47-4315-9C65-71B27E7A2906@gmail.com Backpatch-through: 13-17 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/7f4261d9da35b90d3feb85ea8ea2c7de18913483 Modified Files -------------- doc/src/sgml/release-14.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-05-30 14:22 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-05-30 14:22 pgsql: Fix broken-FK-detection query in release notes Álvaro Herrera <alvherre@kurilemu.de> 2025-05-30 14:22 pgsql: Fix broken-FK-detection query in release notes Álvaro Herrera <alvherre@kurilemu.de> 2025-05-30 14:22 pgsql: Fix broken-FK-detection query in release notes Álvaro Herrera <alvherre@kurilemu.de> 2025-05-30 14:22 pgsql: Fix broken-FK-detection query in release notes Álvaro Herrera <alvherre@kurilemu.de> 2025-05-30 14:22 pgsql: Fix broken-FK-detection query in release notes Álvaro Herrera <alvherre@kurilemu.de>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox