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.
I use it, other than being a bit heavy weight, I love it. Same types of features but to me looks better in a few ways - supports any database, beautiful auto-generated ER diagrams, personally I like the interface better, and to the extent that you don't hate Eclipse it's an advantage that you can install it into a regular Eclipse instance and use any other language / plugin that Eclipse supports (for example editing SQL with vim keybindings). It's actually really cool, for example, working with Django, debugging your code and in the same window having auto-refresh running to show the rows getting added in the DBeaver interface.
Use it and love it. I believe that table plus (or similar ones) are nice and cool, but for me, DBeaver is very powerful and useful piece of software. It may not look cool sometimes, but it gets the job done. And it has a lot of connectors. Plus it is free! I can't expect more.
I tried several clients for Mac a few years ago (including Postico) and DBeaver was the only one not lacking basic features (views & materialized views, triggers, functions, partitions, extensions…). So I've been using it since then.
In addition, I like that the main sidebar shows everything properly categorized and as a tree with collapsing nodes, i.e. servers > databases > schemas > tables, views, materialized views, functions, etc… > columns, constraints, foreign keys, indexes, triggers, partitions, dependencies, references, etc.
Finally, the support is great. I reported some bugs on GitHub and they all have been fixed on the next release, like 1 or 2 weeks after the report.
It was slow on my old Mac, but since I switched to a M1 I have no complaints.
It's big, complex and heavyweight (it's basically an eclipse skin), but if you do a lot of data work with different sources it's definitely your best bet.
It has nice viewer interfaces even for uncommon data types (like geospatial data), and it's well-suited for both infra work and querying.
It's not pretty but it's one of the most useful pieces of software I interact with.
