So what is the intended behaviour?
- If you run everything in autocommit, it will be very slow, but all non-failing records will end up in the table alright.
- If you run a commit after a couple of records, you will lose all records of this group if there is at least one failing record.
is that what you want?
Oracle's behaviour of saving all non-failing records while discarding all failing records is not directly possible with PostgreSQL, because the sense of a transaction is all-or-nothing.
Am 24.11.20 um 16:39 schrieb David G. Johnston:
What is the point of COMMITting after a few records? Why not let the whole batch run through. If there are any errors, PostgreSQL will rollback the whole transaction anyway.
Avoiding that behavior is the point of batching with periodic commits.
David J.
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012