From: Joe Conway <mail@joeconway.com>
To: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maximum Possible Insert Performance?
Date: Sun, 23 Nov 2003 20:40:15 -0800
Message-ID: <3FC18BAF.7070506@joeconway.com> (raw)
In-Reply-To: <bprv1q$1j5o$1@news.hub.org>
References: <bprv1q$1j5o$1@news.hub.org>
William Yu wrote:
> My situation is this. We have a semi-production server where we
> pre-process data and then upload the finished data to our production
> servers. We need the fastest possible write performance. Having the DB
> go corrupt due to power loss/OS crash is acceptable because we can
> always restore from last night and re-run everything that was done since
> then.
If you can, use COPY -- it is far faster than INSERT.
See:
http://www.postgresql.org/docs/current/static/sql-copy.html
HTH,
Joe
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-performance@postgresql.org
Cc: mail@joeconway.com, wyu@talisys.com
Subject: Re: Maximum Possible Insert Performance?
In-Reply-To: <3FC18BAF.7070506@joeconway.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