I recently started receiving this error as well, this was because I
disabled autocommit.
With the following option in .psqlrc the error doesn't wait for a
rollback but automatically creates a savepoint allowing you to fix the
error and continue:
This is now in my .psqlrc:
\set AUTOCOMMIT off
\set
Thanks for the recommendations. Unfortunately I have to clean out the data
before I insert, so I cannot do a bulk copy from a CSV, I will try the
option of inserting into src table and then copying relevant data to dest
table and see if that works faster for me. I suppose I could bulk insert and
th
Samuel Gendler wrote:
On Wed, Jan 4, 2012 at 1:57 AM, Zdravko Balorda
mailto:zdravko.balo...@siix.com>> wrote:
Take it out of transaction. Why is there a transaction in the first
place?
If transaction is needed, ok, but take these inserts out and
everything will
work as it
Well, idea is to make process faster as possible... And usualy staging
table does not have any constrains so can't violates...
When we want to import banch of data... Process when we taking row by
row from source, validate it, if valid insert to some table could be
very slow...
Much faster is whe
On Wed, Jan 4, 2012 at 1:57 AM, Zdravko Balorda wrote:
> Andreas Kretschmer wrote:
>
>> rverghese wrote:
>>
>> I want to insert a bunch of records and not do anything if the record
>>> already
>>> exists. So the 2 options I considered are 1) check if row exists or
>>> insert
>>> and 2) ignore th
Andreas Kretschmer wrote:
rverghese wrote:
I want to insert a bunch of records and not do anything if the record already
exists. So the 2 options I considered are 1) check if row exists or insert
and 2) ignore the unique violation on insert if row exists.
Any opinions on whether it is faster
rverghese wrote:
> I want to insert a bunch of records and not do anything if the record already
> exists. So the 2 options I considered are 1) check if row exists or insert
> and 2) ignore the unique violation on insert if row exists.
> Any opinions on whether it is faster to INSERT and then ca
On 2012-01-03, Misa Simic wrote:
> If exists is better, though insert line by line and check if exists may
> be very slow...
>
> The best would be if you can use copy command from csv to staging table
> (without constraints) and then
>
> Insert to live from stage where stage constraint column not
