Re: minor leaks in pg_dump (PG tarball 10.6)

From: Pavel Raiskup <praiskup(at)redhat(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: minor leaks in pg_dump (PG tarball 10.6)
Date: 2018-12-06 07:00:13
Message-ID: 1757475.ZK10eePKrr@nb.usersys.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, December 5, 2018 4:59:18 PM CET Stephen Frost wrote:
> This change doesn't seem to make any sense to me..? If anything, seems
> like we'd end up overallocating memory *after* this change, where we
> don't today (though an analyzer tool might complain because we don't
> free the memory from it and instead copy the pointer from each of these
> items into the tbinfo structure).

Correct, I haven't think that one through. I was confused that some items
related to the dropped columns could be unreferenced. But those are
anyways allocated as a solid block with others (not intended to be ever
free()'d). Feel free to ignore that.

Thanks for looking at this!
Pavel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2018-12-06 07:08:47 Re: zheap: a new storage format for PostgreSQL
Previous Message Pavel Stehule 2018-12-06 07:00:12 Re: zheap: a new storage format for PostgreSQL