On Sat, Apr 11, 2020 at 10:09:59AM +0200, Peter Eisentraut wrote: > I just fixed a relcache leak that I accidentally introduced (5a1d0c9925). > Because it was a TAP test involving replication workers, you don't see the > usual warning anywhere unless you specifically check the log files manually. > > How about a compile-time option to turn all the warnings in resowner.c into > errors? This could be enabled automatically by --enable-cassert, similar to > other defines that that option enables. >
+1. Would it be worthwhile to do the same in e.g. aset.c (for MEMORY_CONTEXT_CHECKING case), or more generally for stuff in src/backend/utils?
