Re: [WIP] Double-write with Fast Checksums
От | Tom Lane |
---|---|
Тема | Re: [WIP] Double-write with Fast Checksums |
Дата | |
Msg-id | 29764.1326326970@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [WIP] Double-write with Fast Checksums (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: [WIP] Double-write with Fast Checksums
Re: [WIP] Double-write with Fast Checksums |
Список | pgsql-hackers |
Simon Riggs <simon@2ndQuadrant.com> writes: > On Wed, Jan 11, 2012 at 11:07 PM, Josh Berkus <josh@agliodbs.com> wrote: >> On 1/11/12 1:25 PM, Dan Scales wrote: >>> And just wanted to reiterate one other benefit of double writes -- it greatly reduces the size of the WAL logs. >> Even if you're replicating? > Yes, but it will increase random I/O on the standby when we replay if > we don't have FPWs. The question is how you prevent torn pages when a slave server crashes during replay. Right now, the presence of FPIs in the WAL stream, together with the requirement that replay restart from a checkpoint, is sufficient to guarantee that any torn pages will be fixed up. If you remove FPIs from WAL and don't transmit some substitute information, ISTM you've lost protection against slave server crashes. regards, tom lane
В списке pgsql-hackers по дате отправления: