mirror of
https://github.com/postgres/postgres.git
synced 2026-04-12 04:26:44 -04:00
cc398df078
occurring during a reload, such as query-cancel. Instead of zeroing out an existing relcache entry and rebuilding it in place, build a new relcache entry, then swap its contents with the old one, then free the new entry. This avoids problems with code believing that a previously obtained pointer to a cache entry must still reference a valid entry, as seen in recent failures on buildfarm member jaguar. (jaguar is using CLOBBER_CACHE_ALWAYS which raises the probability of failure substantially, but the problem could occur in the field without that.) The previous design was okay when it was made, but subtransactions and the ResourceOwner mechanism make it unsafe now. Also, make more use of the already existing rd_isvalid flag, so that we remember that the entry requires rebuilding even if the first attempt fails. Back-patch as far as 8.2. Prior versions have enough issues around relcache reload anyway (due to inadequate locking) that fixing this one doesn't seem worthwhile. |
||
|---|---|---|
| .. | ||
| catcache.c | ||
| inval.c | ||
| lsyscache.c | ||
| Makefile | ||
| plancache.c | ||
| relcache.c | ||
| syscache.c | ||
| ts_cache.c | ||
| typcache.c | ||