![]() Relying on aggregate information in pg_stat_statementsĮach method has its own advantages and disadvantages, which will be discussed in this document Making use of the PostgreSQL slow query logĪ more traditional way to attack slow queries is to make use of PostgreSQL’s slow query log. ![]() Checking execution plans with auto_explain.Here are my top three suggestions to handle bad performance: However, three methods have proven to really useful to quickly assess a problem. There are many ways to approach performance problems. Finding slow queries and performance weak spots is therefore exactly what this post is all about. When digging into PostgreSQL performance it is always good to know, which option one has to spot performance problems and to figure out, what is really going on on a server. Performance pg_stat_statements postgresql query statistics
0 Comments
Leave a Reply. |