pgsql: Limit depth of forced recursion for CLOBBER_CACHE_RECURSIVELY. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Limit depth of forced recursion for CLOBBER_CACHE_RECURSIVELY.
Date
Msg-id E1fyP1i-0005DU-EV@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Limit depth of forced recursion for CLOBBER_CACHE_RECURSIVELY.

It's somewhat surprising that we got away with this before.  (Actually,
since nobody tests this routinely AFAIK, it might've been broken for
awhile.  But it's definitely broken in the wake of commit f868a8143.)
It seems sufficient to limit the forced recursion to a small number
of levels.

Back-patch to all supported branches, like the preceding patch.

Discussion: https://postgr.es/m/12259.1532117714@sss.pgh.pa.us

Branch
------
REL9_4_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/35e39610a3f83e0464cb2ff2b1e4c282d323b602

Modified Files
--------------
src/backend/utils/cache/inval.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix longstanding recursion hazard in sinval message processing.
Next
From: Tom Lane
Date:
Subject: pgsql: Save/restore SPI's global variables in SPI_connect() andSPI_fin