Timeline for Postgres logging_collector probably blocks auto_explain output
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2018 at 14:13 | vote | accept | Maryna Krasnova | ||
| Sep 7, 2018 at 19:22 | answer | added | jjanes | timeline score: 1 | |
| Sep 7, 2018 at 12:16 | comment | added | Maryna Krasnova | Please add your answer as answer, so I'll mark this as solution. Really, the statistic of slow queries did not displayed immediately because of connection pool was created before log_min_duration was turn on | |
| Aug 21, 2018 at 12:04 | comment | added | Maryna Krasnova | All queries were run from Elixir Phoneix application with pool of connections, and yes, be application was not restarted | |
| Aug 21, 2018 at 11:56 | comment | added | jjanes | Works for me. Could it be that the other long queries were run over existing connections (perhaps with a connection pooler) for which the session_preload_libraries has not taken effect? | |
| Aug 21, 2018 at 10:49 | history | edited | Maryna Krasnova | CC BY-SA 4.0 |
added 250 characters in body; edited title
|
| Aug 21, 2018 at 10:18 | history | asked | Maryna Krasnova | CC BY-SA 4.0 |