| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Limit depth of forced recursion for CLOBBER_CACHE_RECURSIVELY. |
| Date: | 2018-09-07 22:14:54 |
| Message-ID: | E1fyP1i-0005DK-DM@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/f510412df3510e244fb3f9570ba5d2b4d27e773a
Modified Files
--------------
src/backend/utils/cache/inval.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-09-08 00:10:20 | pgsql: Save/restore SPI's global variables in SPI_connect() and SPI_fin |
| Previous Message | Tom Lane | 2018-09-07 22:05:14 | pgsql: Fix longstanding recursion hazard in sinval message processing. |