Skip site navigation (1) Skip section navigation (2)

Re: Inefficient bytea escaping?

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inefficient bytea escaping?
Date: 2006-05-27 15:36:15
Message-ID: e51f66da0605270836h4ea88ce3r768f3bd0eda08c8f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 5/27/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Marko Kreen" <markokr(at)gmail(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2006-05-27 15:46:12
Subject: Re: LIKE, leading percent, bind parameters and indexes
Previous:From: Tom LaneDate: 2006-05-27 14:57:05
Subject: Re: LIKE, leading percent, bind parameters and indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group