Re: Why does this query write to the disk?

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Why does this query write to the disk?
Дата
Msg-id
23587.1221761600@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Why does this query write to the disk? "Nikolas Everett" <nik9000@gmail.com>
Re: Why does this query write to the disk? "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Why does this query write to the disk? Tom Lane <tgl@sss.pgh.pa.us>
Re: Why does this query write to the disk? "Scott Carey" <scott@richrelevance.com>
Re: Why does this query write to the disk? Tom Lane <tgl@sss.pgh.pa.us>
Re: Why does this query write to the disk? "Nikolas Everett" <nik9000@gmail.com>
Re: Why does this query write to the disk? "Scott Carey" <scott@richrelevance.com>
"Kevin Grittner"  writes:
> "Nikolas Everett"  wrote: 
>> I'm a bit confused as to why this query writes to the disk:
 
> It's probably writing hint bits to improve performance of subsequent
> access to the table.  The issue is discussed here:
> http://wiki.postgresql.org/wiki/Hint_Bits

Hint-bit updates wouldn't be WAL-logged.  If the table has been around a
long time, it might be freezing old tuples, which *would* be WAL-logged
(since 8.2 or so) --- but that would be a one-time, non-repeatable
behavior.  How sure are you that there was WAL output?

What I was thinking was more likely was that the hash table for the hash
join was spilling out to temp files.  That wouldn't be WAL-logged
either, but depending on your tablespace setup it might result in I/O on
some other disk than the table proper.

			regards, tom lane
В списке pgsql-performance по дате отправления
От: Kevin Grittner
Дата:
От: Scott Carey
Дата:
FAQ