Re: Streaming I/O, vectored I/O (WIP)

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: Streaming I/O, vectored I/O (WIP)
Дата
Msg-id CA+hUKGLLFvou5rx5FDhm-Pc9r4STQTFFmrx6SUV+vk8fwMbreA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Streaming I/O, vectored I/O (WIP)  (Thomas Munro <thomas.munro@gmail.com>)
Ответы Re: Streaming I/O, vectored I/O (WIP)
Список pgsql-hackers
On Tue, Apr 2, 2024 at 9:39 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> So this is the version I'm going to commit shortly, barring objections.

And done, after fixing a small snafu with smgr-only reads coming from
CreateAndCopyRelationData() (BM_PERMANENT would be
incorrectly/unnecessarily set for unlogged tables).

Here are the remaining patches discussed in this thread.  They give
tablespace-specific io_combine_limit, effective_io_readahead_window
(is this useful?), and up-to-1MB io_combine_limit (is this useful?).
I think the first two would probably require teaching reloption.c how
to use guc.c's parse_int() and unit flags, but I won't have time to
look at that for this release so I'll just leave these here.

On the subject of guc.c, this is a terrible error message... did I do
something wrong?

postgres=# set io_combine_limit = '42MB';
ERROR:  5376 8kB is outside the valid range for parameter
"io_combine_limit" (1 .. 32)

Вложения

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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: Building with musl in CI and the build farm
Следующее
От: Andy Fan
Дата:
Сообщение: Re: using extended statistics to improve join estimates