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

Поиск
Список
Период
Сортировка
От Thomas Kellerer
Тема [GENERAL] Why does a SELECT query cause "dirtied" buffers?
Дата
Msg-id ot015g$ml7$1@blaine.gmane.org
обсуждение исходный текст
Ответы Re: [GENERAL] Why does a SELECT query cause "dirtied" buffers?
Список pgsql-general
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 по дате отправления:

Предыдущее
От: "Zhu, Joshua"
Дата:
Сообщение: Re: [GENERAL] BDR question on dboid conflicts
Следующее
От: Justin Pryzby
Дата:
Сообщение: Re: [GENERAL] Why does a SELECT query cause "dirtied" buffers?