Re: COMMIT NOWAIT Performance Option

Поиск
Список
Период
Сортировка
От Jeff Davis
Тема Re: COMMIT NOWAIT Performance Option
Дата
Msg-id 1172693822.13722.73.camel@dogma.v10.wvs
обсуждение исходный текст
Ответ на Re: COMMIT NOWAIT Performance Option  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Ответы Re: COMMIT NOWAIT Performance Option  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Список pgsql-hackers
On Wed, 2007-02-28 at 14:54 -0500, Jonah H. Harris wrote:
> On 2/28/07, Jeff Davis <pgsql@j-davis.com> wrote:
> > That's 5 minutes of data, in the default configuration.
> 
> Right, but I don't know anyone that keeps checkpoints at 5 minutes.
> At least not on OLTP configurations.
> 

It's got a hard maximum of 1 hour. Also, the need to make checkpoints
far apart has been reduced with bgwriter. It will be further reduced
with the patch that allows people to tune the bgwriter for their needs.

Recovery has to run through all those WAL segments anyway. It's not like
we're making a 5 second recovery take 20 minutes, we'd be taking an
already long recovery and making it longer (I'm not sure how much
longer, but it can't be more than twice as long).

I'm not saying there's no cost, but the extra recovery cost seems lower
to me than the CRC cost on every data page read during operation.

Also, if we find an error, do we even have the ability to correct it? A
CRC doesn't tell us which pages were written and which weren't, so we
could detect the error but not correct it, right?

Regards,Jeff Davis



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

Предыдущее
От: "Saqib Awan"
Дата:
Сообщение: 8.1.8 Installer Fails on Win2k Server
Следующее
От: "Jonah H. Harris"
Дата:
Сообщение: Re: COMMIT NOWAIT Performance Option