diff options
| author | Bruce Momjian <bruce@momjian.us> | 2005-06-04 22:57:22 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2005-06-04 22:57:22 +0000 |
| commit | 24af7d4b68ea5cf08c458ffb00fffacc8c6b7d2c (patch) | |
| tree | dde9346f72c7a9909962ccc56014e5cab2496c36 /src/backend/access/gist/gist.c | |
| parent | 954108f92d5477a4527380c9f867bc9401880975 (diff) | |
| download | postgresql-24af7d4b68ea5cf08c458ffb00fffacc8c6b7d2c.tar.gz postgresql-24af7d4b68ea5cf08c458ffb00fffacc8c6b7d2c.zip | |
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.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions