Re: --enable-thread-safety bug

Tom Lane wrote:
> Steve Clark <sclark(at)netwolves(dot)com> writes:
>
>>The return from malloc should be checked to make sure it succeeds -
>>right???
>
>
> Probably, but what do you expect the code to do if it doesn't succeed?
> This function seems not to have any defined error-return convention.
>
> regards, tom lane
>
>
Retry - the malloc - maybe there is a memory leak when
--enable-thread-saftey is enabled,
send an out of memory message to the postgres log, abort the
transaction - I don't know I am
not a postgres developer so I don't know all the issues. I all I know
as a user having a program
like postgres just sig 11 is unacceptable! As a commercial developer
of software for over 30 years
I would never just do nothing.

My $.02
Steve