Re: COPY speedup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pierre Frédéric Caillaud <lists(at)peufeu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY speedup
Date: 2009-08-12 13:45:30
Message-ID: 9842.1250084730@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?utf-8?Q?Pierre_Fr=C3=A9d=C3=A9ric_Caillau?= =?utf-8?Q?d?= <lists(at)peufeu(dot)com> writes:
> I've been examining the code path for COPY FROM too, and I think it is
> possible to get the same kind of speedups on COPY FROM that the patch in
> the previous message did for COPY TO, that is to say perhaps 2-3x faster
> in BINARY mode and 10-20% faster in TEXT mode (these figures are
> ballparks, only based on very quick checks however).

> The idea is to avoid most (actually, all) palloc()'ing and memcpy()'ing
> for types that are pass-by-value like INT.

> Is there interest in such a patch (for 8.6) ?

If you do as much damage to the I/O function API as the other patch
did, it will probably be rejected. We don't touch datatype APIs
lightly, because it affects too much code.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-08-12 13:55:25 Re: machine-readable explain output v4
Previous Message Andrew Dunstan 2009-08-12 13:42:00 Re: machine-readable explain output v4