]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 614d951) | patch
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)
commita0f863637f15c7f64b9a94cdcb767da27b489399
treeae54e533e65ab9d957c20fda5e54e0d259f39e58tree | snapshot
parent614d951a541c816bf7f53fa5dd82aca21d8ce0d0commit | diff
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 diff | blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git