After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 635926 - postgresql backend: gnclock is not cleared
postgresql backend: gnclock is not cleared
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Backend - SQL
2.3.x
Other Linux
: Normal normal
: ---
Assigned To: Phil Longstaff
Chris Shoemaker
Depends on:
Blocks:
 
 
Reported: 2010-11-27 15:55 UTC by dtbaumann
Modified: 2018-06-29 22:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dtbaumann 2010-11-27 15:55:43 UTC 
This started around version 2.3.16

when opening gnucash I get the following error:

GnuCash could not obtain the lock for postgres://tb:????@localhost/gnucash.

That database may be in use by another user, in which case you should not open it. What would you like to do?

Things work generally ok if I open anyway.

Manually emptying the gnclock table removes the error.

Thanks
Thomas
Comment 1 John Ralls 2010-12-07 23:50:10 UTC 
Fixed in r19912. 

Stupid case-converting, but otherwise case-sensitive, Postgres.
Comment 2 John Ralls 2018-06-29 22:48:29 UTC 
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=635926. Please update any external references or bookmarks.