Bruce Momjian <[EMAIL PROTECTED]> writes:
> What we could do is to throw a compile #error if you hit our own
> snprintf() and are compiling with threads enabled.
Good thought. If we get any complaints then we can reconsider applying
this patch, otherwise there's no need.
Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > Some OSes lack proper snprintf()/vsnprintf() fuctions so PostgreSQL includes
> > its own version (src/port/snprintf.c) during building. Unfortunately, this
> > version of snprintf() is not reentrant (it uses global vars to k
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Some OSes lack proper snprintf()/vsnprintf() fuctions so PostgreSQL includes
> its own version (src/port/snprintf.c) during building. Unfortunately, this
> version of snprintf() is not reentrant (it uses global vars to keep internal
> state),
The following bug has been logged online:
Bug reference: 1044
Logged by: Denis Stepanov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Any OS lacking proper snprintf()
Description:snprintf() shipped with PostgreSQL is not thread safe
D
