Re: Bug in DefineRange() with multiranges - Mailing list pgsql-hackers

From Sergey Shinderuk
Subject Re: Bug in DefineRange() with multiranges
Date
Msg-id f50a7e90-b166-b41d-3a7d-c0344974446e@postgrespro.ru
Whole thread Raw
In response to Re: Bug in DefineRange() with multiranges  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Bug in DefineRange() with multiranges
List pgsql-hackers
On 10.10.2021 20:12, Peter Eisentraut wrote:
> On 04.10.21 19:09, Sergey Shinderuk wrote:
>> I wonder what is the proper fix.  Just drop pfree() altogether or add
>> pstrdup() instead?  I see that makeMultirangeTypeName() doesn't bother
>> freeing its buf.
> 
> I think removing the pfree()s is a correct fix.
> 

Thanks, here is a patch.


-- 
Sergey Shinderuk        https://postgrespro.com/

Attachment

pgsql-hackers by date:

Previous
From: Ants Aasma
Date:
Subject: Re: storing an explicit nonce
Next
From: Dilip Kumar
Date:
Subject: Re: Error "initial slot snapshot too large" in create replication slot