Search Postgresql Archives

Why does a SELECT query cause "dirtied" buffers?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux