supabase__supabase

mirror of https://github.com/supabase/supabase.git synced 2026-09-22 13:37:53 +08:00

Files

T

History

Vaibhav c427615234 fix(pg-meta): pair composite foreign key columns correctly (#41080 )

## TL;DR

Correctly pairs composite foreign key columns when loading table
metadata.

## What's hurting?

The tables introspection query matched every source column in a
composite foreign key with every target column. For `(user_id,
tenant_id) → (id, tenant_id)`, it returned four relationships instead of
the correct two, causing incorrect relationship metadata in the Table
Editor...

## Now fixed

Source and target columns are paired by ordinal position using a lateral
multi-array `unnest`.
Regression coverage now verifies adversarial column ordering, and the
existing performance guard exercises thousands of composite foreign
keys...

PS: local stress test found no performance regression or unexpected
sequential scans.

## Ref

- Closes #41068

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* Corrected foreign-key relationship detection for composite keys,
ensuring source and target columns are paired accurately.
* Improved catalog relationship queries to remain within performance
limits for composite-key tables.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>

2026-09-10 19:35:52 +02:00

catalog-plan-guard.test.ts

fix(pg-meta): pair composite foreign key columns correctly (#41080 )

2026-09-10 19:35:52 +02:00

fdw.test.ts

fix(pg-meta): escape unencrypted FDW server options via format() %L (#47014 )

2026-06-22 15:45:56 +08:00

get-users-common.test.ts

Organize pg meta queries for studio (#43562 )

2026-03-10 09:34:11 +07:00

get-users-count.test.ts

Organize pg meta queries for studio (#43562 )