Back out patch:

Bruce Momjian <bruce@momjian.us>

Commit: 24af7d4b68ea5cf08c458ffb00fffacc8c6b7d2c
Author: Bruce Momjian <bruce@momjian.us>
Date: 2005-06-04T22:57:22Z
Releases: 8.1.0
Back out patch:

---------------------------------------------------------------------------

Tom Lane <tgl@sss.pgh.pa.us> writes:
> a_ogawa <a_ogawa@hi-ho.ne.jp> writes:
> > It is a reasonable idea. However, the majority part of MemSet was not
> > able to be avoided by this idea. Because the per-tuple contexts are used
> > at the early stage of executor.
>
> Drat.  Well, what about changing that?  We could introduce additional
> contexts or change the startup behavior so that the ones that are
> frequently reset don't have any data in them unless you are working
> with pass-by-ref values inside the inner loop.

That might be possible. However, I think that we should change only
aset.c about this article.
I thought further: We can check whether context was used from the last
reset even when blocks list is not empty. Please see attached patch.

Files

PathChange+/−
src/backend/utils/mmgr/aset.c modified +1 −12