Postgres Pro
Downloads
Home   >   mailing lists

Re: Use pgBufferUsage for block reporting in analyze - Mailing list pgsql-hackers

From Karina Litskevich
Subject Re: Use pgBufferUsage for block reporting in analyze
Date
Msg-id CACiT8iZyeyjWWW4T1sNW7PCra8DXAbj7vi6cQQUbWR0PauskqQ@mail.gmail.com
Whole thread Raw
In response to Re: Use pgBufferUsage for block reporting in analyze  (Karina Litskevich <litskevichkarina@gmail.com>)
Responses Re: Use pgBufferUsage for block reporting in analyze
List pgsql-hackers
Tree view
I wrote:

I suggest assigning values
bufferusage.shared_blks_read + bufferusage.local_blks_read
and
bufferusage.shared_blks_dirtied + bufferusage.local_blks_dirtied
to new variables and using them. This would keep the changed lines within
the 80 symbols limit, and make the code more readable overall.

The same applies to
bufferusage.shared_blks_hit + bufferusage.local_blks_hit

pgsql-hackers by date:

Previous
From: Karina Litskevich
Date:
Subject: Re: Use pgBufferUsage for block reporting in analyze
Next
From: Erik Wienhold
Date:
Subject: Re: XML test error on Arch Linux