From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: When using postgresql backend and choosing 'Generlal Ledger' from the menu, I get and error message from guile: Application "/usr/bin/guile" has crashes due to a fatal error (Segmentation fault) then, it just exits. Version-Release number of selected component (if applicable): gnucash-backend-postgres-1.8.12-0.fc4 How reproducible: Always Steps to Reproduce: 1. open file using postgres backend 2. go to 'Tools' 3. choose 'General Ledger' Actual Results: Error: pgendGetResults: failed to get result to query: ERROR: syntax error at or near ")" at character 315 Error: pgend_trans_commit_edit: send query failed: another command is already in progress Error: pgendTransactionGetDeleted...(): send query failed: another command is already in progress Error: pgendCopyTransactionToEngi...(): no such transaction in the database. This is unexpected ... Error: xaccTransRollbackEdit: Rollback Failed. Ouch! Error: pgendGetResults: failed to get result to query: ERROR: syntax error at or near ")" at character 315 Error: pgend_trans_commit_edit: send query failed: another command is already in progress Error: pgendTransactionGetDeleted...(): send query failed: another command is already in progress Error: pgendCopyTransactionToEngi...(): no such transaction in the database. This is unexpected ... Error: xaccTransRollbackEdit: Rollback Failed. Ouch! Expected Results: when using the normal (not postgresql) backend, a transaction window opens. Additional info:
*** Bug 177647 has been marked as a duplicate of this bug. ***
In a message from the upstream developers: .... None of the developers recommend using the Postgres code. It hasn't been maintained in a long time, and it is not feature complete. If you're using any feature added since 1.6 (which means any business objects, scheduled transactions, etc) then it /will/ crash using postgres. .... As such, this is not something Red Hat or Fedora will fix locally; in fact, I'll probably just disable the postgres backend in future builds, given this information.