From: terry@greatgulfhomes.com
To: Postgres (E-mail) <pgsql-docs@postgresql.org>
Subject: COPY optimization issue
Date: Thu, 13 Jun 2002 09:15:26 -0400
Message-ID: <003901c212dc$627a9120$2766f30a@development.greatgulfhomes.com> (raw)
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@greatgulfhomes.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: terry@greatgulfhomes.com
Subject: Re: COPY optimization issue
In-Reply-To: <003901c212dc$627a9120$2766f30a@development.greatgulfhomes.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox