Re: [HACKERS] WAL logging freezing

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] WAL logging freezing
Дата
Msg-id 22033.1162258828@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] WAL logging freezing  ("Simon Riggs" <simon@2ndquadrant.com>)
Ответы Re: [HACKERS] WAL logging freezing  ("Simon Riggs" <simon@2ndquadrant.com>)
Список pgsql-patches
"Simon Riggs" <simon@2ndquadrant.com> writes:
> That was understood; in the above example I agree you need to flush. If
> you don't pass a truncation point, you don't need to flush whether or
> not you actually truncate. So we don't need to flush *every* time,

OK, but does that actually do much of anything for your performance
complaint?  Just after GlobalXmin has passed a truncation point, *every*
vacuum the system does will start performing a flush-n-fsync, which
seems like exactly what you didn't like.  If the syncs were spread out
in time for different rels then maybe this idea would help, but AFAICS
they won't be.

            regards, tom lane

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

Предыдущее
От: "Simon Riggs"
Дата:
Сообщение: Re: --single-transaction doc clarification
Следующее
От: Neil Conway
Дата:
Сообщение: Re: --single-transaction doc clarification