Re: Why our Valgrind reports suck - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why our Valgrind reports suck
Date
Msg-id 446633.1746808350@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why our Valgrind reports suck  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> Briefly looking through the leaks indeed quickly found a real seeming leak,
> albeit of limited size:
> ProcessStartupPacket() does
>     buf = palloc(len + 1);
> in TopMemoryContext() without ever freeing it.

Yeah, I saw that too.  Didn't seem worth doing anything about it
unless we make pretty massive cleanups elsewhere.

> I have wondered if we ought to have some infrastructure to tear down all
> relcache, catcache entries (and other similar things) before shutdown if
> MEMORY_CONTEXT_CHECKING is enabled. That would make it a lot easier to see
> leaks at shutdown. We certainly have had leaks in relcache etc...

I'd be content if all that stuff was shown as "still reachable".

            regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL 18 Beta 1 release announcement draft
Next
From: Peter Geoghegan
Date:
Subject: Re: Adding skip scan (including MDAM style range skip scan) to nbtree