Re: pg_dump: fix memory leak - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: pg_dump: fix memory leak
Date
Msg-id F60FA5E1-A42A-4E4A-AD61-A7E93B854D4A@yesql.se
Whole thread Raw
In response to Re: pg_dump: fix memory leak  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
> On 29 Aug 2025, at 11:52, Álvaro Herrera <alvherre@kurilemu.de> wrote:

> Hmm, this begs the question -- why do we make generate_restrict_key()
> return NULL in that case?  Maybe we should redefine its contract to be
> that it either returns a valid key, or it calls pg_fatal().  Then
> callers don't have to worry about it.

That is certainly an option.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Assert single row returning SQL-standard functions
Next
From: Pavel Stehule
Date:
Subject: Re: Assert single row returning SQL-standard functions