Skip site navigation (1) Skip section navigation (2)

Re: ETL optimization

From: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
To: Bricklen Anderson <BAnderson(at)PresiNET(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: ETL optimization
Date: 2005-06-24 04:27:21
Message-ID: Pine.LNX.4.44.0506240624350.4501-100000@zigo.dhs.org (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, 23 Jun 2005, Bricklen Anderson wrote:

> iii. UNIQUE constraint on table "t1". This didn't seem to perform too
> badly with fewer rows (preliminary tests), but as you'd expect, on error
> the whole transaction would roll back. Is it possible to skip a row if
> it causes an error, as opposed to aborting the transaction altogether?

You don't need to roll back the whole transaction if you use savepoints or 
the exception features in pl/pgsql

Take a look at this example:

http://developer.postgresql.org/docs/postgres/plpgsql-control-structures.html#PLPGSQL-UPSERT-EXAMPLE

-- 
/Dennis Björklund


In response to

Responses

pgsql-performance by date

Next:From: Scott GoldsteinDate: 2005-06-24 04:32:54
Subject: Postgres 8 vs Postgres 7.4/cygwin
Previous:From: Bricklen AndersonDate: 2005-06-23 22:04:33
Subject: Re: ETL optimization

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group