Re: confusing checkpoint_flush_after / bgwriter_flush_after

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: confusing checkpoint_flush_after / bgwriter_flush_after
Дата
Msg-id alpine.DEB.2.20.1611252232100.29326@lancre
обсуждение исходный текст
Ответ на Re: confusing checkpoint_flush_after / bgwriter_flush_after  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Ответы Re: confusing checkpoint_flush_after / bgwriter_flush_after
Список pgsql-hackers
Дерево обсуждения 
>> What we do in some similar cases is put the burden on initdb to fill in
>> the correct value by modifying postgresql.conf.sample appropriately.
>> It seems like that could be done easily here too.  And it'd be a
>> back-patchable fix.
>
> I haven't realized initdb can do that. I agree that would be the best
> solution.

Indeed.

Maybe something like the following, or maybe it should include "bufmgr.h",
not sure.

--
Fabien.
Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [sqlsmith] Failed assertion in parallel worker in ExecInitSubPlan
Следующее
От: Jim Nasby
Дата:
Сообщение: References to arbitrary database objects that are suitable for pg_dump