| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Pierre Frédéric Caillaud <lists(at)peufeu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY speedup |
| Date: | 2009-08-12 16:00:31 |
| Message-ID: | 20090812160031.GJ5721@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure escribió:
> 2009/8/12 Pierre Frédéric Caillaud <lists(at)peufeu(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2009-08-12 16:02:20 | Re: machine-readable explain output v4 |
| Previous Message | Stefan Kaltenbrunner | 2009-08-12 15:54:07 | surprising trigger/foreign key interaction |