Re: long transaction

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Sabin Coanda" <sabin(dot)coanda(at)deuromedia(dot)ro>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: long transaction
Date: 2008-08-12 16:56:29
Message-ID: b42b73150808120956ie421dbcl2c24d486c8793eb9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Aug 12, 2008 at 4:17 AM, Sabin Coanda
<sabin(dot)coanda(at)deuromedia(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message H. Hall 2008-08-12 18:43:42 Re: Using PK value as a String
Previous Message Mark Mielke 2008-08-12 15:56:22 Re: Using PK value as a String