Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Inefficient bytea escaping?
- From: "Marko Kreen" <markokr(at)gmail(dot)com>
- To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
- Cc: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "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: Tue, 30 May 2006 10:44:31 +0300
- Message-id: <e51f66da0605300044i5f98addld40d9351a7a69d2a(at)mail(dot)gmail(dot)com>
On 5/30/06, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> 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. So your patch to src/backend/storage/file/fd.c should be discarded? OK.
Yes. It was just for experimenting. As I understand Tom already rewrote the critical path. -- marko
- References:
- Re: Inefficient bytea escaping?
- From: Marko Kreen
- Re: Inefficient bytea escaping?
- From: Bruce Momjian
- Re: Inefficient bytea escaping?
- Prev by Date: Re: type recv/send functions
- Next by Date: plperl's ppport.h out of date?
- Previous by thread: Re: Inefficient bytea escaping?
- Next by thread: Re: Inefficient bytea escaping?
- Indexes: