Re: Load distributed checkpoint
От | Kevin Grittner |
---|---|
Тема | Re: Load distributed checkpoint |
Дата | |
Msg-id | 4579529C.EE98.0025.0@wicourts.gov обсуждение исходный текст |
Ответ на | Re: Load distributed checkpoint ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: Load distributed checkpoint
Re: Load distributed checkpoint |
Список | pgsql-hackers |
>>> On Fri, Dec 8, 2006 at 11:01 AM, in message <4579461A.EE98.0025.0@wicourts.gov>, "Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote: I'm going to correct a previous statement, based on having just chatted with a member of the web team. The remaining dribble of these was only occurring on the Windows machines. (We were running two servers from Windows and two from Linux for a while to see how things compared.) The settings I previously posted have completely eliminated the problem on Linux, and we are moving all servers to Linux, so this has become a total non-issue for us. I really encourage people to try some much more aggressive background writer settings, and possibly try tuning the OS dirty write settings. Unless PostgreSQL gets much closer to the hardware than the community consensus seems to support, I don't understand what you could do in the checkpoint phase that would improve on that. (That, of course, doesn't mean I'm not missing something, just that the arguments made so far haven't shown me that the suggested changes would do anything but move the problem around a little bit.) -Kevin
В списке pgsql-hackers по дате отправления: