- Initial Release: Repository initialized!
- Added a menu to browse all queries in
myqueries.json
. - Integrated pgTune for PostgreSQL tuning (pgTune).
- Implemented Bootstrap Data Tables for enhanced UI.
- Added estimated rows count to the dashboard.
- Added loading spinners for better user feedback.
- Fixed dashboard bug for PostgreSQL versions < 14 (conflict counting issue).
- Introduced the ability to use DDL to query LLMs.
- Improved LLM responses with Markdown formatting.
- Optimized the Docker image.
- Added table statistics display.
- Introduced ranked queries functionality.
- Enabled support for local LLMs like Ollama.
- Enhanced LLM prompts with Markdown formatting.
- Add specific documentation for LLM usage.
- Optimize LLM queries
- Optimize gunicorn configuration.
- Run Pg Assistant recommandations on database
- Missing indexes on FK.
- On analyze query, try to identify data type of a parameter. Try to get 10 values of this parameter to help the user provide parameters
- Use sql-formatter to format SQL
- Adding an issue query : find foreign keys with wrong data type
- Adding autovacuum=on to docker-compose parameter
- When a query has more than 9 parameters, parameter replacement fails.
- Add comments on EXPLAIN ANALYZE to help dev understand the output of an EXPLAIN ANALYZE result.
- In the statistics view, add columns involved in the queries and operation types. Next step in v1.8: check if indexes exist on these columns (goal: recommend missing indexes to optimize queries).
- Top queries bug with postgresql 17 : pg_stat_statements missing columns with this version
- Upgrade base docker image to get the latest postgresql client : v17.
- Filter queries that can not be used in an EXPLAIN ANALYZE query
- Enable pg_stat_statment at connexion.
- Some LLM seams to forget that primary keys are always indexed. Changing the LLM prompt to fix that.
- Fix issues/7
- Fix issues/5 (I hope so)
- Help dev to find a primary key. See a sample result here on primary key issues;
- For each table and schema, ask the LLM if the table definitions comply with relevant RFC(s). See sample here
- Somebody notice that on foreign keys issues (missing indexes), the suggest query did not use the CREATE INDEX CONCURRENTLY. pgAssistant should be used BEFORE to get in production, but a quick copy/paste maybe dangerous.
- With postgresql v17, pgTune is not working