Re: COPY speedup - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: COPY speedup
Date
Msg-id 20090812160031.GJ5721@alvh.no-ip.org
Whole thread Raw
In response to Re: COPY speedup  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: COPY speedup  (Pierre Frédéric Caillaud<lists@peufeu.com>)
List pgsql-hackers
Merlin Moncure escribió:
> 2009/8/12 Pierre Frédéric Caillaud <lists@peufeu.com>:
> >
> >
> >> If you do as much damage to the I/O function API as the other patch
> >> did, it will probably be rejected.
> >
> >        You mean, as the COPY patch in my previous message, or as another
> > patch ?
> >        (I just search the archives and found one about CopyReadLine, but
> > that's probably not what you are talking about)
> >
> >> We don't touch datatype APIs
> >> lightly, because it affects too much code.
> >>
> >>                        regards, tom lane
> >
> >        I definitely agree with that.
> 
> Is there any way to do this that is not as invasive?

Maybe add new methods, fastrecv/fastsend etc.  Types that don't
implement them would simply use the slow methods, maintaining
backwards compatibility.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: surprising trigger/foreign key interaction
Next
From: Csaba Nagy
Date:
Subject: Re: machine-readable explain output v4