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

From Michael Paquier
Subject Re: Bug in DefineRange() with multiranges
Date
Msg-id YWZesfUmF5pnyd8X@paquier.xyz
Whole thread Raw
In response to Re: Bug in DefineRange() with multiranges  (Sergey Shinderuk <s.shinderuk@postgrespro.ru>)
Responses Re: Bug in DefineRange() with multiranges  (Sergey Shinderuk <s.shinderuk@postgrespro.ru>)
List pgsql-hackers
On Tue, Oct 12, 2021 at 08:52:29AM +0300, Sergey Shinderuk wrote:
> Thanks, here is a patch.

Looks fine seen from here, so I'll apply shortly.  I was initially
tempted to do pstrdup() on the object name returned by
QualifiedNameGetCreationNamespace(), but just removing the pfree() is
simpler.

I got to wonder about similar mistakes from the other callers of
QualifiedNameGetCreationNamespace(), so I have double-checked but
nothing looks wrong.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless opclass makes index and table unusable
Next
From: Michael Paquier
Date:
Subject: Re: Reset snapshot export state on the transaction abort