Postgres Pro
Downloads
Home   >   mailing lists

[GENERAL] Why does a SELECT query cause "dirtied" buffers? - Mailing list pgsql-general

From Thomas Kellerer
Subject [GENERAL] Why does a SELECT query cause "dirtied" buffers?
Date
Msg-id ot015g$ml7$1@blaine.gmane.org
Whole thread Raw
Responses Re: [GENERAL] Why does a SELECT query cause "dirtied" buffers?  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-general
Tree view 
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

pgsql-general by date:

Previous
From: "Zhu, Joshua"
Date:
Subject: Re: [GENERAL] BDR question on dboid conflicts
Next
From: Justin Pryzby
Date:
Subject: Re: [GENERAL] Why does a SELECT query cause "dirtied" buffers?