PostgreSQL has doesn't use rollback segment, so commit over 10000 lines is not necessary, and it is bad.
If you are having database in your laptop it might be true. In OLTP environments it's not feasible to have large transactions a) because of locking problems b) lot's of databases use some kind of replication to have fail over databases doing large updates in such environments causes problems.
We use data_maintainer.py script from SkyTools package to do such updates.
> Hello! > > I want to translate the following Oracle PL/SQL script into plpgsql. > Especially I'm having problems with the transaction thing. i tried START > TRANSACTION and COMMIT without success. > > Any ideas? > > Thanx. > > Ciao, > Gerhard > > CREATE OR REPLACE PROCEDURE insert_1Mio > IS > maxcommit NUMBER; > BEGIN > maxcommit := 10000; > > FOR i IN 1..1000000 LOOP > INSERT INTO employee (id, department, firstname, lastname) VALUES (i, i, > 'John' || to_char(i), 'Smith' || to_char(i)); > IF MOD(i, maxcommit) = 0 THEN > COMMIT; > END IF; > END LOOP; > > COMMIT; > END; > > > > -- > http://www.wiesinger.com/ > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
