diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2025-02-09 13:43:56 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2025-02-09 13:43:56 +0100 |
| commit | 9926f854d07784d72aada16c8038b558fbc45d13 (patch) | |
| tree | 2e7d34e49253006b039e61b281aa077a795c8e1b /src/fe_utils/string_utils.c | |
| parent | a9258629edabd461f998ec7d06cdf554e8a6a6ec (diff) | |
| download | postgresql-9926f854d07784d72aada16c8038b558fbc45d13.tar.gz postgresql-9926f854d07784d72aada16c8038b558fbc45d13.zip | |
Cache NO ACTION foreign keys separately from RESTRICT foreign keys
Now that we generate different SQL for temporal NO ACTION vs RESTRICT
foreign keys, we should cache their query plans with different keys.
Since the key also includes the constraint oid, this shouldn't be
necessary, but we have been seeing build farm failures that suggest we
might be sometimes using a cached NO ACTION plan to implement a RESTRICT
constraint.
Author: Paul A. Jungwirth <pj@illuminatedcomputing.com>
Discussion: https://www.postgresql.org/message-id/flat/CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com
Diffstat (limited to 'src/fe_utils/string_utils.c')
0 files changed, 0 insertions, 0 deletions