Neat! Just added it to my "Postgres Is Enough" gist:<p><a href="https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f06dbb#performance-tuning" rel="nofollow">https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f...</a>
> OpenAI helper: If you have an OpenAI account, the interface can query OpenAI to help you understand your query plan and optimize your SQL queries<p>How good are LLMs at optimizing queries? Do they just give basic advices like "try adding an index there" or can they do more?<p>I guess it would need to cross the results of the explain analyze with at least the DDLs of the table (including partitions, indexes, triggers, etc), and like the sizes of the tables and the rate of reads/writes of the tables in some cases, to be able to "understand" and "reason" about what's going on and offer meaningful advices (e.g. proposing design changes for the tables).<p>I don't see how a generic LLM would be able to do that, but maybe another type of model trained for this task and with access to all the information it needs?
The screenshot section in the README seems to be empty. Would've been interesting to see that. There's many tools that do similar things like <a href="https://github.com/ankane/pghero">https://github.com/ankane/pghero</a> or some tools here: <a href="https://gitlab.com/postgres-ai" rel="nofollow">https://gitlab.com/postgres-ai</a>
honest question: does anybody know a good book/tutorial/source/whatever on becoming a postgresql DBA ?<p>most of the material i see is written for people that want to write applications that work with postgresql, not on how to proficiently manage postgresql itself.
Added this to the performance tuning section: <a href="https://github.com/Olshansk/postgres_for_everything?tab=readme-ov-file#performance-tuning">https://github.com/Olshansk/postgres_for_everything?tab=read...</a>
This reminds me of a less feature-rich version of PgAnalyze, but it's always nice to have alternative OSS options for this sort of optimization work.
Your screenshot for issues found show indices being created with CREATE INDEX. If someone runs that on a prod DB with a large table, they’re gonna have a bad time. You should have it suggest CREATE INDEX CONCURRENTLY.<p>Also, if I’m being honest, it’s a little off-putting to see a tool giving advice on Postgres and not differentiating between those two.