When creating an invoice and using a tax table to caclulate the tax on sale or purchase, the 
invoice total may display (and use) more than two decimal places. 
 
When one then posts the bill/invoice, the following is produced: 
 
Enter: gnc_lot_init: (lot=0x837beb8, book=0x83b4de0) 
Leave: gnc_lot_init: (lot=0x837beb8, book=0x83b4de0) 
Enter: gnc_lot_add_split: (lot=0x837beb8, split=0x834ab28) 
Error: pgendStoreOneKVPtimespecOn...(): finish query failed: 
        ERROR:  value too long for type character(4) 
 
Error: pgendStoreAuditKVPtimespec...(): send query failed: 
        another command is already in progress 
 
Error: pgendGetCache: send query failed: 
        another command is already in progress 
 
Error: pgendGetCache: send query failed: 
        another command is already in progress 
 
Error: pgend_trans_commit_edit: send query failed: 
        another command is already in progress 
 
Enter: gnc_lot_remove_split: (lot=0x837beb8, split=0x834ab28) 
Warning: PrintAmountInternal: max_decimal_places too small; limit 2, value 75.0177 
Warning: PrintAmountInternal: max_decimal_places too small; limit 2, value 75.0177 
Warning: PrintAmountInternal: max_decimal_places too small; limit 2, value 75.0177 
 
Following such a post, the next time you try to save your data the followin error is produced 
and GnuCash opens a save as dialogue to allow you to save the data into a file. 
 
The server at URL 
 
postgres://localhost/mydata?mode=single-update experienced an error or encountered bad or 
corrupt data. 
 
Of course, when you re-start GnuCash, the incvoice/bill is not in the database.