From: Sabin Coanda <sabin.coanda@deuromedia.ro>
To: pgsql-performance@postgresql.org
Subject: Re: long transaction
Date: Wed, 13 Aug 2008 09:07:49 +0300
Message-ID: <g7ttnc$1on8$1@news.hub.org> (raw)
References: <g5qd5o$1ot3$1@news.hub.org>
<120621.32315.qm@web59503.mail.ac4.yahoo.com>
<g7onk7$12sj$1@news.hub.org>
<b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com>
<g7rgtr$1cc0$1@news.hub.org>
<b42b73150808120956ie421dbcl2c24d486c8793eb9@mail.gmail.com>
>
> have you considered importing to a temporary 'holding' table with
> copy, then doing 'big' sql statements on it to check constraints, etc?
>
Yes I considered it, but the problem is the data is very tight related
between different tables and is important to keep the import order of each
entity into the database. With other words, the entity imprt serialization
is mandatory. In fact the import script doesn't keep just insert but also
delete and update for different entities. So copy is not enough. Also using
'big' sql statements cannot guarantee the import order.
Sabin
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: sabin.coanda@deuromedia.ro
Subject: Re: long transaction
In-Reply-To: <g7ttnc$1on8$1@news.hub.org>
* 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