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

From Marko Kreen
Subject Re: Inefficient bytea escaping?
Date
Msg-id e51f66da0605270836h4ea88ce3r768f3bd0eda08c8f@mail.gmail.com
Whole thread Raw
In response to Re: Inefficient bytea escaping?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Inefficient bytea escaping?
List pgsql-hackers
On 5/27/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Marko Kreen" <markokr@gmail.com> writes:
> > If you want to use fwrite as string operator, then maybe
> > should replace it with fwrite_unlocked?
>
> ISTM that in a single-threaded application such as the backend,
> it should be libc's responsibility to avoid such overhead, not
> ours.

Obviously, except glibc guys seems to be philosophically
opposed to this, so apps need to work around it.

AFAIK at least *BSDs have got this right, don't know
about others.

-- 
marko


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: LIKE, leading percent, bind parameters and indexes
Next
From: Martijn van Oosterhout
Date:
Subject: Re: LIKE, leading percent, bind parameters and indexes