Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..
Дата
Msg-id CA+TgmoaTthmnFNqTD_xbGaxSg6jO8oT_VLfyUKpW71dQFC_-oQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Ответы Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Дерево обсуждения 
On Mon, Apr 16, 2018 at 2:13 AM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
> The code that detects sequential behavior can not distinguish between
> pread() and lseek+read, it looks only at the actual offset of the
> current request compared to the previous one for the same fp.
>
>  Thomas> +1 for adopting pread()/pwrite() in PG12.
>
> ditto

Likewise.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Следующее
От: Jerry Sievers
Дата:
Сообщение: Re: Racing DEADLOCK on PostgreSQL 9.3