Discussion
Query Tool¶
chaz6: When I got the update I looked through the settings and there appears to be no way to disable it. I do not want AI anywhere near my database. I only use it for testing/staging at least so I should hopefully not have to worry about it wrecking production.
aitchnyu: Might as well choose our AI subscription for our tools. I always hated the sparkle icons in Mongodb Compass (db browsing tool), Cloudwatch (logs) etc which is wired to a useless model. So I always chose to write Python scripts to query Postgres and other DBs and render pretty tables to CLI.
hombre_fatal: It will be nice when AI agents can use apps more generally so everyone doesn't have to build and maintain a bespoke AI widget for their app.
imjared: The docs suggest that you can set the default provider to "None" to disable AI features: https://www.pgadmin.org/docs/pgadmin4/9.13/preferences.html#...
smartbit: Note: AI features must be enabled in the server configuration LLM_ENABLED = True in config.py for these preferences to be available.
zenmac: It is nice that they have the default set to "None". However to have this feature in pgAmdin is as distraction from the project.If it is just calling API anyway, then I don't want to have this in my db admin tool. It also expose surface area of potential data leakage.
naranha: The only interface that works for me efficiently with LLMs is the chatbot interface. I rather copy and paste snippets into the chat box than have IDEs and other tools guess what I might want to ask AI.The first thing I do with these integration is look how I can remove them.
vavkamil: Quick fix based on https://github.com/pgadmin-org/pgadmin4/issues/9696#issuecom...Click on the "Reset layout" button in the query tool (located in the top right corner), and it will move the "AI Assistant" tab to the right. Now, when you query a table, it will default to the Query tab as always.
stuaxo: If I can use this with a local LLM it could be useful.
zbentley: Yeah. This seems like an area where a “tiny” (2-4GB) local model would be more than sufficient to generate very high quality queries and schema answers to the vast majority of questions. To the point that it feels outright wasteful to pay a frontier model for it.
panzi: Yeah, no thanks. I switched to dbeaver already anyway, because pgadmin was annoying about to which postgres versions it could connect. Too much of a hassle to setup a new version from source back when I tried. With dbeaver I just run ./dbeaver from the extracted .tag.gz. dbeaver is also not a web interface, but a real desktop application (Java, though).
OptionOfT: I did not enable this and yet I got the panel in the UI.
