On Nov 26, 2010, at 11:52 PM, Johann Wöckinger wrote: > Hi, > > here is the gnucash.trace generated by one complete session (start, > overriding lock message, close): > ---------------------------------------------------------- > * 08:47:27 CRIT <gnc.backend.dbi> [pgsql_error_fn()] DBI error: FEHLER: > Relation »gnclock« existiert bereits > > * 08:47:27 CRIT <gnc.backend.dbi> gnc_dbi_set_error: assertion `dbi_conn != > NULL' failed > * 08:47:28 CRIT <gnc.backend.dbi> [pgsql_error_fn()] DBI error: FEHLER: > Relation »gnclock« existiert bereits > > * 08:47:28 CRIT <gnc.backend.dbi> gnc_dbi_set_error: assertion `dbi_conn != > NULL' failed > * 08:47:28 WARN <qof.engine> [gnc_iso8601_to_timespec_gmt()] mktime failed > to handle daylight saving: tm_hour=0 tm_year=70 tm_min=0 tm_sec=0 tm_isdst=-1 > for string=1970-01-01 00:00:00 > ..... ~4500 Entrys like the above > * 08:48:08 WARN <gnc.backend.dbi> [gnc_dbi_unlock()] No lock table in > database, so not unlocking it. > ---------------------------------------------------------- > > can it be, that gnucash tries to create the lock table (not only the lock > entry) in each session ? >
Sorry, I forgot about this until Bug 635926 [1]. Fixed now in r19912. The problem was that I'd used an upper-case name for the lock table, and the combination of dbi and postgres doesn't like that. So Postgres would create and populate the table but not be able to find it during shutdown. Regards, John Ralls [1] https://bugzilla.gnome.org/show_bug.cgi?id=635926 _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
