| From: | terry(at)greatgulfhomes(dot)com |
|---|---|
| To: | "Postgres (E-mail)" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | COPY optimization issue |
| Date: | 2002-06-13 13:15:26 |
| Message-ID: | 003901c212dc$627a9120$2766f30a@development.greatgulfhomes.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
My postgres database does a nightly sync with a Legacy database by
clobbering a postgres table with data from a CSV.
I currently just use the COPY command, but with over 800,000 records, this
takes quite some time.
Is there a faster way?
eg I notice that any validation failure of ANY records causes the entire
copy to roll back. Is this begin/commit action wrapped around the copy
costing me CPU cycles? And if so, can I turn it off, or is there a better
way then using copy?
Note: I do nightly vacuum's so deleted tuples is not the issue, I don't
think.
Thanks
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry(at)greatgulfhomes(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-06-13 13:52:30 | Re: COPY optimization issue |
| Previous Message | Bruce Momjian | 2002-06-08 04:23:43 | Re: Updated Russian version of FAQ |