| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alan Li <ali(at)truviso(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.4 open item: copy performance regression? |
| Date: | 2009-06-22 17:37:04 |
| Message-ID: | 39156D9B-6755-4EF0-99AD-C4539E45A952@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le 22 juin 2009 à 17:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> I was thinking it might be beneficial to be able to defer writing WAL
>> until COPY is complete, so heap_sync would either fsync the whole
>> heap
>> file or copy the whole file to WAL.
>
> What about indexes?
Skip this optimisation if there are any.
It's already Common practise to create them only after copy succeeded
when possible for better bulk loading perfs.
Then there's also the copy + Insert ... Select ... technique.
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-22 17:55:04 | Re: BUG #4862: different results in to_date() between 8.3.7 & 8.4.RC1 |
| Previous Message | Brendan Jurd | 2009-06-22 17:16:08 | Re: BUG #4862: different results in to_date() between 8.3.7 & 8.4.RC1 |