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 11:15:41
Message-ID: e51f66da0605270415g64a49f23ue3cf8805ba9012d8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/27/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > I'm off for a little visit with oprofile...
>
> It seems the answer is that fwrite() does have pretty significant
> per-call overhead, at least on Fedora Core 4.

That may be because of the locking ritual all stdio functions
like to do, even without _REENTRANT.

If you want to use fwrite as string operator, then maybe
should replace it with fwrite_unlocked?

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Pflug 2006-05-27 11:51:50 Re: XLogArchivingActive
Previous Message Hannu Krosing 2006-05-27 08:05:44 Re: Updatable views/with check option parsing