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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Inefficient bytea escaping?


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
  • Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
  • Subject: Re: Inefficient bytea escaping?
  • Date: Thu, 25 May 2006 14:46:37 -0400
  • Message-id: <14749(dot)1148582797(at)sss(dot)pgh(dot)pa(dot)us>

Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> Tom Lane wrote:
>> Looking at CopySendData, I wonder whether any traction could be gained
>> by trying not to call fwrite() once per character.  I'm not sure how
>> much per-call overhead there is in that function.  We've done a lot of
>> work trying to optimize the COPY IN path since 8.0, but nothing much
>> on COPY OUT ...

> Hm, I'll see whether I can manage to check CVS head too, and see what's 
> happening, not a production alternative though.

OK, make sure you get the copy.c version I just committed ...

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group