Re: long transaction

From: "Sabin Coanda" <sabin(dot)coanda(at)deuromedia(dot)ro>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: long transaction
Date: 2008-08-13 06:07:49
Message-ID: g7ttnc$1on8$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>
> 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2008-08-13 06:17:44 Re: Filesystem benchmarking for pg 8.3.3 server
Previous Message Ron Mayer 2008-08-13 04:28:32 Re: Filesystem benchmarking for pg 8.3.3 server