| From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inefficient bytea escaping? |
| Date: | 2006-05-28 11:45:39 |
| Message-ID: | e51f66da0605280445l18b12d1cw1587cfa34437e983@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/28/06, Martijn van Oosterhout <kleptog(at)svana(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-05-28 12:32:04 | Error in recent pg_dump change (coverity) |
| Previous Message | Rémi Zara | 2006-05-28 09:00:17 | Re: osprey buildfarm member has been failing for a long while |