> On 29 Aug 2025, at 09:36, m.korot...@postgrespro.ru wrote: > > Daniel Gustafsson wrote 2025-08-29 10:13: >> This is not actually a leak since the application will terminate immediately >> if >> a restrict key cannot be generated. > I agree that the current usage of the function does not present a problem, > but there is no certainty that this situation will remain unchanged.
I certainly hope it won't change, ignoring a failure from pg_strong_random() is a seriously bad idea. If the function is rewritten to change its errorhandling then allocation might be changed, right now there is no leak and no bug. -- Daniel Gustafsson
