Re: Inefficient bytea escaping? - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Inefficient bytea escaping?
Date
Msg-id e51f66da0605280445l18b12d1cw1587cfa34437e983@mail.gmail.com
Whole thread Raw
In response to Re: Inefficient bytea escaping?  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Inefficient bytea escaping?
Re: Inefficient bytea escaping?
List pgsql-hackers
On 5/28/06, Martijn van Oosterhout <kleptog@svana.org> 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


pgsql-hackers by date:

Previous
From: Rémi Zara
Date:
Subject: Re: osprey buildfarm member has been failing for a long while
Next
From: Martijn van Oosterhout
Date:
Subject: Error in recent pg_dump change (coverity)