| From: | frank church <pgsql(at)adontendev(dot)net> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Loading lots of data in a SQL command |
| Date: | 2006-01-04 01:32:11 |
| Message-ID: | 1136338331.43bb259b9334f@webmail.adontendev.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
I am load lots of data via SQL into a database and wrapping it into transactions
speeds it up.
However this fails a number of times. The queries results are logged so it is
easy for me to find problem records.
However a single failure causes the whole transaction to fail.
Is there a setting or feature that allows which allows the same performance as
transactions, without causing the whole process to fail, like a delayed updates
or write mechanism of some sort.
It is something I would like to set in that particular data looad.
Frank
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-01-04 02:42:47 | Re: getting a query column to return 0 if nothing matches |
| Previous Message | Dan Tenenbaum | 2006-01-03 22:15:25 | getting a query column to return 0 if nothing matches |