Re: performance statistics monitoring without spamming logs

2018-07-13 Thread Julien Rouhaud
On Fri, Jul 13, 2018 at 9:23 AM, Adrien NAYRAT wrote: > On 07/13/2018 12:25 AM, Lukas Fittl wrote: >> >> On Tue, Jul 10, 2018 at 11:38 AM, Justin Pryzby > > wrote: >> >> > 2. Make stats available in `pg_stat_statements` (or alternate view >> that >> > could be

Re: performance statistics monitoring without spamming logs

2018-07-13 Thread Adrien NAYRAT
On 07/10/2018 08:38 PM, Justin Pryzby wrote: On Tue, Jul 10, 2018 at 01:54:12PM -0400, Patrick Hemmer wrote: I'm looking for a way of gathering performance stats in a more usable way than turning on `log_statement_stats` (or other related modules). The problem I have with the log_*_stats family

Re: performance statistics monitoring without spamming logs

2018-07-13 Thread Adrien NAYRAT
On 07/13/2018 12:25 AM, Lukas Fittl wrote: On Tue, Jul 10, 2018 at 11:38 AM, Justin Pryzby > wrote: > 2. Make stats available in `pg_stat_statements` (or alternate view that > could be joined on). The block stats are already available here, but > others l

Re: performance statistics monitoring without spamming logs

2018-07-12 Thread Lukas Fittl
On Tue, Jul 10, 2018 at 11:38 AM, Justin Pryzby wrote: > > > 2. Make stats available in `pg_stat_statements` (or alternate view that > > could be joined on). The block stats are already available here, but > > others like CPU usage, page faults, and context switches are not. > > pg_stat_statements

Re: performance statistics monitoring without spamming logs

2018-07-10 Thread Justin Pryzby
On Tue, Jul 10, 2018 at 01:54:12PM -0400, Patrick Hemmer wrote: > I'm looking for a way of gathering performance stats in a more usable > way than turning on `log_statement_stats` (or other related modules). > The problem I have with the log_*_stats family of modules is that they > log every single

performance statistics monitoring without spamming logs

2018-07-10 Thread Patrick Hemmer
I'm looking for a way of gathering performance stats in a more usable way than turning on `log_statement_stats` (or other related modules). The problem I have with the log_*_stats family of modules is that they log every single query, which makes them unusable in production. Aside from consuming sp