pgsql: Fix an O(N^2) problem in foreign key references. - Mailing list pgsql-committers

From Kevin Grittner
Subject pgsql: Fix an O(N^2) problem in foreign key references.
Date
Msg-id E1ZaSzE-0007q7-2k@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix an O(N^2) problem in foreign key references.

Commit 45ba424f improved foreign key lookups during bulk updates
when the FK value does not change.  When restoring a schema dump
from a database with many (say 100,000) foreign keys, this cache
would grow very big and every ALTER TABLE command was causing an
InvalidateConstraintCacheCallBack(), which uses a sequential hash
table scan.  This could cause a severe performance regression in
restoring a schema dump (including during pg_upgrade).

The patch uses a heuristic method of detecting when the hash table
should be destroyed and recreated.
InvalidateConstraintCacheCallBack() adds the current size of the
hash table to a counter.  When that sum reaches 1,000,000, the hash
table is flushed.  This fixes the regression without noticeable
harm to the bulk update use case.

Jan Wieck
Backpatch to 9.3 where the performance regression was introduced.

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/7d0712890d1e18379394cec33b01edb7102928de

Modified Files
--------------
src/backend/utils/adt/ri_triggers.c |   38 ++++++++++++++++++++++++++++++++---
1 file changed, 35 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: When trace_lwlocks is used, identify individual lwlocks by name.
Next
From: Kevin Grittner
Date:
Subject: pgsql: Fix an O(N^2) problem in foreign key references.