ToeBee/ChangesetMD

synchronous_commit

Opened this issue · 2 comments

If the server with postgres crashes there is no way to restore an interrupted upload. It is therefore safe to use synchronous_commit, as the data is lost anyways.

synchronous_commit should be set to off, with SQL like SET synchronous_commit TO OFF;

Will this actually get me anything though? Since I'm doing everything inside of a single huge transaction I don't think this would actually get me any kind of measurable performance boost.

Not that I can see - you're creating a new cursor for each changeset and doing an INSERT at https://github.com/ToeBee/ChangesetMD/blob/master/changesetmd.py#L56