Support non-btree indexes for foreign keys Previously, only btrees were supported as the referenced unique index for foreign keys because there was no way to get the equality strategy number for other index methods. We have this now (commit c09e5a6a016), so we can support this. In fact, this is now just a special case of the existing generalized "period" foreign key support, since that already knows how to lookup equality strategy numbers.
Note that this does not change the requirement that the referenced index needs to be unique, and at the moment, only btree supports that, so this does not change anything in practice, but it would allow another index method that has amcanunique to be supported. Co-authored-by: Mark Dilger <mark.dil...@enterprisedb.com> Discussion: https://www.postgresql.org/message-id/flat/e72eaa49-354d-4c2e-8eb9-255197f55...@enterprisedb.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/bfe21b760e039163b91279f58fd09a0298572775 Modified Files -------------- src/backend/commands/tablecmds.c | 57 ++++++++++++++++------------------------ 1 file changed, 23 insertions(+), 34 deletions(-)
