Postgres Pro
Downloads
Home   >   mailing lists

Thread: [GENERAL] Why does a SELECT query cause "dirtied" buffers?

[GENERAL] Why does a SELECT query cause "dirtied" buffers?

From
Thomas Kellerer
Date:
When using explain (analyze, buffers) things like this can show up:
        Buffers: shared hit=137 read=6545 dirtied=46

Given the description in the manual:
    The number of blocks dirtied indicates the number of previously unmodified blocks that were changed by this query

I am a bit surprised why a SELECT (read-only) query would cause buffers to be dirtied?

Under which situation does a SELECT query change a block?

Regards
Thomas 




-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Why does a SELECT query cause "dirtied" buffers?

From
Justin Pryzby
Date:
On Fri, Oct 27, 2017 at 09:24:40PM +0200, Thomas Kellerer wrote:
> Under which situation does a SELECT query change a block?

https://wiki.postgresql.org/wiki/Hint_Bits


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general