Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Inefficient bytea escaping?
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Marko Kreen" <markokr(at)gmail(dot)com>
- Cc: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Inefficient bytea escaping?
- Date: Sat, 27 May 2006 10:12:11 -0400
- Message-id: <22900(dot)1148739131(at)sss(dot)pgh(dot)pa(dot)us>
"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. regards, tom lane
- Follow-Ups:
- Re: Inefficient bytea escaping?
- From: Marko Kreen
- Re: Inefficient bytea escaping?
- References:
- Inefficient bytea escaping?
- From: Andreas Pflug
- Re: Inefficient bytea escaping?
- From: Tom Lane
- Re: Inefficient bytea escaping?
- From: Andreas Pflug
- Re: Inefficient bytea escaping?
- From: Tom Lane
- Re: Inefficient bytea escaping?
- From: Andreas Pflug
- Re: Inefficient bytea escaping?
- From: Tom Lane
- Re: Inefficient bytea escaping?
- From: Tom Lane
- Re: Inefficient bytea escaping?
- From: Tom Lane
- Re: Inefficient bytea escaping?
- From: Marko Kreen
- Inefficient bytea escaping?
- Prev by Date: Re: Updatable views/with check option parsing
- Next by Date: Re: LIKE, leading percent, bind parameters and indexes
- Previous by thread: Re: Inefficient bytea escaping?
- Next by thread: Re: Inefficient bytea escaping?
- Indexes: