Re: [HACKERS] Memory not freed at WARN

> > This all didn't matter until we have triggers and constraints
> > now. One normal action of a trigger or constraint is to fire
> > a transaction abort. Thus, a really long running database
> > backend can grow and grow.
> >
> > Please add this to TODO as I don't have the time right now to
> > dive into.
>
> Never got onto the TODO :-(
>
> It still happens. Seems like approx 1K isn't freed per elog(ERROR).

Added:

* elog() does not free all its memory(Jan)

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)