>no, it's not faster. FYI, gbak uses 1 transaction to restore the whole
>table, and this is the fastest way to insert data.

 Maybe, but it works on exclusive mode - no other connection can be made to database. I think that this is a special case.
I am no expert but I've learned like 10 years ago that in multiuser environment short transactions are preffered.

>seems that you have something in your application, that buffer records
>that are inserted, so, the more inserts, the slower process.

Indeed I've mixed commiting transaction with closing it. In my test I am making commit per 100 rows and closing transaction after 10000 rows.