| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: A little COPY speedup |
| Date: | 2007-03-02 18:54:18 |
| Message-ID: | 15472.1172861658@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Of what use is the above comment? You have to parse the input into
>> fields somehow.
> Well those two requirements aren't inconsistent if you're using fixed-width
> input text files. Not that I'm enamoured of such file formats, just saying.
[ shrug... ] And of course, shoving a large quantity of padding spaces
through the software has zero cost.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-03-02 19:10:43 | Re: A little COPY speedup |
| Previous Message | Tom Lane | 2007-03-02 18:51:32 | Re: [HACKERS] Deadlock with pg_dump? |