Re: ETL optimization - Mailing list pgsql-performance

From Dennis Bjorklund
Subject Re: ETL optimization
Date
Msg-id Pine.LNX.4.44.0506240624350.4501-100000@zigo.dhs.org
Whole thread Raw
In response to ETL optimization  (Bricklen Anderson <BAnderson@PresiNET.com>)
Responses Re: ETL optimization
List 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


pgsql-performance by date:

Previous
From: Bricklen Anderson
Date:
Subject: Re: ETL optimization
Next
From: Scott Goldstein
Date:
Subject: Postgres 8 vs Postgres 7.4/cygwin