aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/giststrat.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2001-01-23 20:36:30 +0000
committerBruce Momjian <bruce@momjian.us>2001-01-23 20:36:30 +0000
commitedfca4b98b44f336ca88b2adf4dfbe6b59d7b146 (patch)
tree2bcc7fa39bf826c07fbd978c21f813289d8f1f17 /src/backend/access/gist/giststrat.c
parent3de8407ea7d3c6d3343242ed72cefd4a51373861 (diff)
downloadpostgresql-edfca4b98b44f336ca88b2adf4dfbe6b59d7b146.tar.gz
postgresql-edfca4b98b44f336ca88b2adf4dfbe6b59d7b146.zip
Subject: Bug in SQLForeignKeys()
Query used for checking foreign key triggers returns too many results when there're more than one foreign key in a table. It happens because only table's oid is used to link between pg_trigger with INSERT check and pg_trigger with UPDATE/DELETE check. I think there should be enough to add following conditions into WHERE clause of that query: AND pt.tgconstrname = pg_trigger.tgconstrname AND pt.tgconstrname = pg_trigger_1.tgconstrname /Constantin
Diffstat (limited to 'src/backend/access/gist/giststrat.c')
0 files changed, 0 insertions, 0 deletions