Re: Collection of memory leaks for ECPG driver - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: Collection of memory leaks for ECPG driver
Date
Msg-id 20150613092513.GB14175@feivel.credativ.lan
Whole thread Raw
In response to Re: Collection of memory leaks for ECPG driver  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Collection of memory leaks for ECPG driver  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Sat, Jun 13, 2015 at 12:02:40AM -0400, Tom Lane wrote:
> But having said that, I would not be in a hurry to remove any existing
> if-guards for the case.  For one thing, it makes the code look more
> similar to backend code that uses palloc/pfree, where we do *not* allow
> pfree(NULL).  There's also the point that changing longstanding code
> creates back-patching hazards, so unless there's a clear gain it's best
> not to.

Makes sense, but there is no point in adding hos if-guards to old code that
doesn't have it either,right?

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Incompatible trig error handling
Next
From: deavid
Date:
Subject: Re: Is it possible to have a "fast-write" Index?