Re: Collection of memory leaks for ECPG driver
От | Michael Paquier |
---|---|
Тема | Re: Collection of memory leaks for ECPG driver |
Дата | |
Msg-id | CAB7nPqTSJ6nBYz_i6v93=3V=UC6BOE-htm3-PTks7O8xM3MpZw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Collection of memory leaks for ECPG driver (Michael Meskes <meskes@postgresql.org>) |
Ответы |
Re: Collection of memory leaks for ECPG driver
|
Список | pgsql-hackers |
On Fri, Jun 12, 2015 at 10:01 PM, Michael Meskes <meskes@postgresql.org> wrote: > On Mon, Jun 08, 2015 at 10:50:25PM +0900, Michael Paquier wrote: > Right, that's because they were developed before free received the safeguard, or the programmer simply didn't know at thatpoint in time. Unless I'm mistaken we have other code that only calls free() without an additional safeguard, so whyshuld ecpglib be special? If you don't like it using both approaches, feel free to remove the check in the other case.:) Well, I can send patches... > More seriously, though, does anyone know of any platform where free(NULL) is *not* a noop? I recall reading that some past versions of SunOS crashed, but it is rather old... -- Michael
В списке pgsql-hackers по дате отправления: