Re: --enable-thread-safety bug

On Sat, Mar 22, 2008 at 12:42:51PM -0400, Tom Lane wrote:
> > Do you create and destroy a lot of threads since it seems this memory
> > won't be freed?
>
> The OP's program isn't threaded at all, since he was apparently running
> with a non-threaded ecpg/libpq before. This means that the proposal of
> looping till someone else frees memory is at least as silly as allowing
> the core dump to happen.

I found an old report where someone found that the get/setspecific
wasn't working and it was allocating a new version of the structure
each time.

http://www.mail-archive.com/pgsql-general(at)postgresql(dot)org/msg42918.html

That was on Solaris though. It would be instructive to test that by
calling that function multiple times successivly and ensure it's
returning the same addess each time.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.