Re: COPY FROM performance improvements

From: "Luke Lonergan" <llonergan(at)greenplum(dot)com>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: "Alvaro Herrera" <alvherre(at)surnet(dot)cl>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Alon Goldshuv" <agoldshuv(at)greenplum(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY FROM performance improvements
Date: 2005-06-27 18:52:30
Message-ID: BEE59901.7E8E%llonergan@greenplum.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-patches pgsql-performance

Andrew,

> You might like to look at running pgindent (see src/tools/pgindent) over
> the file before cutting a patch. Since this is usually run over each
> file just before a release, the only badness should be things from
> recent patches.

I've attached two patches, one gained from running pgindent against the
current CVS tip copy.c (:-D) and one gained by running the COPY FROM perf
improvements through the same. Nifty tool!

Only formatting changes in these.

- Luke

Attachment Content-Type Size
copy-pgindent.patch application/octet-stream 79.7 KB
fast_copy_V12_8.1.patch application/octet-stream 125.9 KB

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Jim C. Nasby 2005-06-27 19:20:15 Re: Problem with dblink regression test
Previous Message Heikki Linnakangas 2005-06-27 17:37:01 Re: [PATCHES] Cleaning up unreferenced table files

Browse pgsql-performance by date

  From Date Subject
Next Message Andrew Dunstan 2005-06-27 20:20:24 Re: COPY FROM performance improvements
Previous Message Bricklen Anderson 2005-06-27 18:15:06 Re: ETL optimization