You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Queries obtained from pg_stat_statement often contain embedded comments which often contain a semicolon. This causes index_advisor to throw an error even though the semicolon doesn't exist in the actual SQL statement.
To fix this, queries should be run through a function to strip embedded comments:
I've tested the regex and it's been solid for me. These comments happen 100% of the time if you look at pg_stat_statements for a project that uses the javascript library (PostgREST).
Queries obtained from
pg_stat_statement
often contain embedded comments which often contain a semicolon. This causesindex_advisor
to throw an error even though the semicolon doesn't exist in the actual SQL statement.To fix this, queries should be run through a function to strip embedded comments:
The text was updated successfully, but these errors were encountered: