On Mon, 10 Jul 2000, Tom Lane wrote:
And my patch ? :-)
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >> --- and BTW. this Dllist design stand in the way for query cache :-)
>
> > That Dllist really has to be removed and made to use the existing
> > routines, if possible.
>
> Yeah, that dllist stuff is on my hit list for memory rewrite. It should
> be using palloc().
Yes. It is a long "malloc-list". IMHO if we have standard chunks and
pfree() is not a problem, we not need malloc. We can *always* use some
context. Now is malloc() very often used for persistent allocation, but it
is posible via some persistent context too. Or exist some real matter for
malloc()?
Karel
...malloc list:
bootstrap/bootstrap.c
bootstrap/bootparse.c
bootstrap/bootscanner.c
commands/async.c
commands/sequence.c
executor/spi.c
lib/dllist.c
parser/gram.c
parser/scan.c
port/dynloader/aix.c
port/dynloader/nextstep.c
port/nextstep/port.c
postmaster/postmaster.c
regex/engine.c
regex/regcomp.c
regex/regexec.c
storage/buffer/localbuf.c
storage/file/fd.c
storage/ipc/ipc.c
storage/ipc/sinval.c
tioga/Varray.c
tioga/tgRecipe.c
utils/fmgr/dfmgr.c
utils/cache/inval.c
utils/error/elog.c
utils/init/findbe.c
utils/init/globals.c
utils/init/miscinit.c
utils/misc/guc-file.l
utils/misc/guc.c
utils/misc/ps_status.c
utils/misc/guc-file.c