Since the tool is in its nascent stages, I reported only a handful of
reports that I myself looked at felt that they were potentially bugs.
I appreciate everyone's feedback.
Best,
Ted
On May 2, 2004, at 4:50 PM, Tom Lane wrote:
Neil Conway <[EMAIL PROTECTED]> writes:
The problem with applying this kind of static analysis to PostgreSQL
is
that palloc() is not like malloc(): if the return value goes out of
scope before it is freed, it is NOT necessarily the case that a memory
leak has occurred.
I'm a bit surprised that a tool unaware of this fact would generate
only
four complaints ... I'd have expected hundreds.
I concur with Neil's opinion that none of the backend cases represent
bugs. However:
[BUG] memory leak on error path (dtype != DTK_DELTA)
File where bug occurred:
postgresql-7.4.2/src/interfaces/ecpg/pgtypeslib/interval.c
Looks suspicious to me, but ECPG is Michael Meskes' domain -- Michael?
It's entirely likely that ecpg's derivative of the backend's datetime
modules contains lots and lots of memory leaks, since AFAIK the palloc
infrastructure is not there in the ecpg environment :-(.
regards, tom lane
---------------------------(end of
broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
