DmitryNFomin

please see below output from one of databases `select wait_event_type, wait_event, state from pg_stat_activity where state = 'active'` ``` wait_event_type | wait_event | state -----------------+---------------+-------- Activity | WalSenderMain | active...

Thanks a lot! that really great explanation. just last last question - why NULL wait_event are filtered out? we loose some part of database activity in the report, especially on...

Hey everyone that's interesting coincidence, I also wanted similar enhancement to explain my idea better I created this PR https://github.com/postgrespro/pg_wait_sampling/pull/95 if you thing it's good idea, I would add code...

I've added logic for _history view to that PR

@Medvecrab many thanks for this. Performance penalty is exact risk that I would like to avoid while still want to have some extra dimensions. If we add fields from PGROC...

agree with your point, just one more comment, can we add isBackgroundWorker from PGPROC? I understand that backend_type is more detailed, but it we can get it without performance penalty...

> So for now we will think of how to carefully add new fields that were discussed in #94 (maybe all of them, maybe some of them, maybe will add...