| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Pierre Frédéric Caillaud <lists(at)peufeu(dot)com> |
| Cc: | 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 15:49:47 |
| Message-ID: | b42b73150908120849o42f12642pd19fc1d9198df3b1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-08-12 15:53:26 | Re: WIP: getting rid of the pg_database flat file |
| Previous Message | Andrew Dunstan | 2009-08-12 15:41:19 | Re: machine-readable explain output v4 |