formatting
Source Link
Andriy M
  • 20.9k
  • 6
  • 51
  • 91

In our production one of the biggest tabletables had this log:

pages: 0 removed, 1801722 remain
tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable
buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied
avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s
system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec
pages: 0 removed, 1801722 remain
tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable
buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied
avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s
system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec

This is by far the worst resource consumption, all other tables have taken less than 2 s.

To see these types of logs you should execute this:

alter system set log_autovacuum_min_duration TO 5; 

(for 5 ms), reload the configuration file.

In our production one of the biggest table had this log

pages: 0 removed, 1801722 remain
tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable
buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied
avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s
system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec

This is by far the worst resource consumption, all other tables have taken less than 2 s.

To see these types of logs you should execute this:

alter system set log_autovacuum_min_duration TO 5; 

(for 5 ms), reload the configuration file.

In our production one of the biggest tables had this log:

pages: 0 removed, 1801722 remain
tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable
buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied
avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s
system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec

This is by far the worst resource consumption, all other tables have taken less than 2 s.

To see these types of logs you should execute this:

alter system set log_autovacuum_min_duration TO 5; 

(for 5 ms), reload the configuration file.

formatting
Source Link
mustaccio
  • 20.3k
  • 17
  • 47
  • 60

In our production one of the biggest table had this log pages: 0 removed, 1801722 remain tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec This

pages: 0 removed, 1801722 remain
tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable
buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied
avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s
system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec

This is by far the worst resource consumption, all other tables have taken less than 2s2 s.

To see these types of logs you should execute this alter system set log_autovacuum_min_duration TO 5; :

alter system set log_autovacuum_min_duration TO 5; 

(for 5ms5 ms) reload, reload the configuration file.

In our production one of the biggest table had this log pages: 0 removed, 1801722 remain tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec This is by far the worst resource consumption, all other tables have taken less than 2s.

To see these types of logs you should execute this alter system set log_autovacuum_min_duration TO 5; (for 5ms) reload the configuration file.

In our production one of the biggest table had this log

pages: 0 removed, 1801722 remain
tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable
buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied
avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s
system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec

This is by far the worst resource consumption, all other tables have taken less than 2 s.

To see these types of logs you should execute this:

alter system set log_autovacuum_min_duration TO 5; 

(for 5 ms), reload the configuration file.

Source Link

In our production one of the biggest table had this log pages: 0 removed, 1801722 remain tuples: 238912 removed, 42582083 remain, 1396 are dead but not yet removable buffer usage: 9477565 hits, 3834218 misses, 2220101 dirtied avg read rate: 2.976 MB/s, avg write rate: 1.723 MB/s system usage: CPU 68.47s/177.49u sec elapsed 10065.08 sec This is by far the worst resource consumption, all other tables have taken less than 2s.

To see these types of logs you should execute this alter system set log_autovacuum_min_duration TO 5; (for 5ms) reload the configuration file.