Why should I disable autocommit while dumping a database?

Turn off autocommit and just do one commit at the end. (In plain SQL, this means issuing BEGIN at the start and COMMIT at the end) If you allow each insertion to be committed separately, PostgreSQL is doing a lot of work for each row that is added. An additional benefit of doing all insertions in one transaction is that if the insertion of one row were to fail then the insertion of all rows inserted up to that point would be rolled back, so you won’t be stuck with partially loaded data.
  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

Manage Database Roles

Solution Database roles are conceptually completely separate from operating system users....

Manage Tablespaces

Tablespaces in PostgreSQL allow database administrators to define locations in the file system...

ColdFusion DSN parameters are not updated

SYMPTOMS New CF DSN records are created.  Even the set of parameters is tried to be updated...

Finding what packages are installed on a Linux system

For distributions that use RPM format packages, use the command: $ rpm -qa You may want to pipe...

What platforms does Linux support?

Linux runs on almost every general-purpose computer made in the last 10 years. It runs on systems...