On Tue, Aug 12, 2008 at 4:17 AM, Sabin Coanda <[EMAIL PROTECTED]> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance