From: Merlin Moncure <mmoncure@gmail.com>
To: Sabin Coanda <sabin.coanda@deuromedia.ro>
Cc: pgsql-performance@postgresql.org
Subject: Re: long transaction
Date: Tue, 12 Aug 2008 12:56:29 -0400
Message-ID: <b42b73150808120956ie421dbcl2c24d486c8793eb9@mail.gmail.com> (raw)
In-Reply-To: <g7rgtr$1cc0$1@news.hub.org>
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>
On Tue, Aug 12, 2008 at 4:17 AM, Sabin Coanda
<sabin.coanda@deuromedia.ro> wrote:
>> long running transactions can be evil. is there a reason why this has
>> to run in a single transaction?
>
> This single transaction is used to import new information in a database. I
> need it because the database cannot be disconected from the users, and the
> whole new data has to be consistently. There are different constraints that
> are checked during the import.
have you considered importing to a temporary 'holding' table with
copy, then doing 'big' sql statements on it to check constraints, etc?
merlin
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: mmoncure@gmail.com, sabin.coanda@deuromedia.ro
Subject: Re: long transaction
In-Reply-To: <b42b73150808120956ie421dbcl2c24d486c8793eb9@mail.gmail.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