I've just seen what happens when the MEMORY_CONTEXT_CHECKING code fires
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 5 Dec 2000 23:40:36 +0000 (23:40 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 5 Dec 2000 23:40:36 +0000 (23:40 +0000)
commitd890bcdf33d9515b8db47b9ff315639036cc2208
tree1f83167586ea98879478e54f6c7c546bc6dbb19f
parentcde0c44dd7f0587324abfa1d7dcdfb7af5e82739
I've just seen what happens when the MEMORY_CONTEXT_CHECKING code fires
an error at end of transaction ... and I did *not* like it.  Reduce ERROR
to NOTICE so that this situation doesn't cause an infinite loop.
src/backend/utils/mmgr/aset.c