Re: Inefficient bytea escaping?

On 5/28/06, Martijn van Oosterhout  wrote:
> With -lpthread
> lock.enabled     323s
> lock.disabled     50s
> lock.unlocked     36s

I forgot to test with -lpthread, my bad.  Indeed by default
something less expensive that full locking is going on.

> The crux of the matter is though, if you're calling something a million
> times, you're better off trying to find an alternative anyway. There is
> a certain amount of overhead to calling shared libraries and no amount
> of optimisation of the library is going save you that.

The crux of the matter was if its possible to use fwrite
as easy string combining mechanism and the answer is no,
because it's not lightweight enough.

-- 
marko