Re: limiting hint bit I/O

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: limiting hint bit I/O
Дата
Msg-id 4D334A010200002500039688@gw.wicourts.gov
обсуждение исходный текст
Ответ на limiting hint bit I/O  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: limiting hint bit I/O  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas  wrote:
> I think you may be confused about what the patch does - currently,
> pages with hint bit changes are considered dirty, period.
> Therefore, they are written whenever any other dirty page would be
> written: by the background writer cleaning scan, at checkpoints,
> and when a backend must write a dirty buffer before reallocating it
> to hold a different page. The patch keeps the first of these and
> changes the second two
No, I understood that.  I'm just concerned that if you eliminate the
other two, we may be recomputing visibility based on clog often
enough to kill performance.
In other words, I'm asking that you show that the other two methods
aren't really needed for decent overall performance.
-Kevin


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: We need to log aborted autovacuums
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Spread checkpoint sync