Optimize query for information_schema.constraint_column_usage

Peter Eisentraut <peter_e@gmx.net>

Commit: e3a58c8835a2cd428b8534dd8df30a7cb96c976b
Author: Peter Eisentraut <peter_e@gmx.net>
Date: 2017-02-18T00:32:15Z
Releases: 10.0
Optimize query for information_schema.constraint_column_usage

The way the old query was written prevented some join optimizations
because the join conditions were hidden inside a CASE expression.  With
a large number of constraints, the query became unreasonably slow.  The
new query performs much better.

From: Alexey Bashtanov <bashtanov@imap.cc>
Reviewed-by: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>

Files

PathChange+/−
src/backend/catalog/information_schema.sql modified +2 −2