Re: Bug in DefineRange() with multiranges

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Alex Kozhemyakin <a(dot)kozhemyakin(at)postgrespro(dot)ru>
Subject: Re: Bug in DefineRange() with multiranges
Date: 2021-10-10 17:12:30
Message-ID: 2d3a3eb1-5a88-da6b-556f-0d7700af52e1@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-10-10 17:17:10 Re: pgsql: Adjust configure to insist on Perl version >= 5.8.3.
Previous Message Peter Eisentraut 2021-10-10 14:07:43 Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set