3 ms·
I once somehow managed to get dbeaver keep a table locked on our prod db, just by having the program open. I thought I was long done doing the things i needed t
by skrebbel 5y ago
I once somehow managed to get dbeaver keep a table locked on our prod db, just by having the program open. I thought I was long done doing the things i needed to do, i just hadn't closed the program.
Then we shipped a release which included a migration. The lock prevented the migration from happening and it took us 30 minutes (of downtime!) to figure out that it was my DBeaver client holding a table hostage. I closed the app and a few seconds later the migration was done and we were up.
Now, obviously this was noobness on my part, somehow, but iirc there was no clear indication in the UI that there was an uncommitted transaction going on or anything like that. I'm sure the problem was between keyboard and chair, but I never dared touch DBeaver after that.
- waingake 5y agoLol also had a similar thing happen. I think they auto close idle transactions now. But I'm very careful about disconnecting when done now!