Re: Patch for fail-back without fresh backup
От
Greg Stark
Тема
Re: Patch for fail-back without fresh backup
Дата
Msg-id
CAM-w4HOUTVj8u0OB=5Cp9DJgnDeDNQkqj+t4sfjsL80Mb4iOww@mail.gmail.com
Ответ на
Re: Patch for fail-back without fresh backup (Heikki Linnakangas)
Список
Дерево обсуждения
Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Amit Kapila <amit.kapila@huawei.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Tom Lane <tgl@sss.pgh.pa.us>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Jeff Davis <pgsql@j-davis.com>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Jeff Davis <pgsql@j-davis.com>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Simon Riggs <simon@2ndQuadrant.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Tom Lane <tgl@sss.pgh.pa.us>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Greg Stark <stark@mit.edu>
Re: Patch for fail-back without fresh backup Tom Lane <tgl@sss.pgh.pa.us>
Re: Patch for fail-back without fresh backup Greg Stark <stark@mit.edu>
Re: Patch for fail-back without fresh backup Simon Riggs <simon@2ndQuadrant.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Simon Riggs <simon@2ndQuadrant.com>
Re: Patch for fail-back without fresh backup Robert Haas <robertmhaas@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Peter Eisentraut <peter_e@gmx.net>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Peter Eisentraut <peter_e@gmx.net>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Sameer Thakur <samthakur74@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Fujii Masao <masao.fujii@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Fujii Masao <masao.fujii@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Fujii Masao <masao.fujii@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Fujii Masao <masao.fujii@gmail.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Fujii Masao <masao.fujii@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Andres Freund <andres@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Robert Haas <robertmhaas@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Amit Langote <amitlangote09@gmail.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Sawada Masahiko <sawada.mshk@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Simon Riggs <simon@2ndQuadrant.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
Re: Patch for fail-back without fresh backup Benedikt Grundmann <bgrundmann@janestreet.com>
Re: Patch for fail-back without fresh backup Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Patch for fail-back without fresh backup Samrat Revagade <revagade.samrat@gmail.com>
On Fri, Jun 14, 2013 at 12:20 PM, Heikki Linnakangas wrote: > For pg_rewind, we wouldn't actually need a full-page image for hint bit > updates, just a small record saying "hey, I touched this page". And you'd > only need to write that the first time a page is touched after a checkpoint. I would expect that to be about the same cost though. The latency for the fsync on the wal record before being able to flush the buffer is the biggest cost. > The proposed patch is clearly not 9.3 material either. If anything, there's > a much better change that we could still sneak in a GUC to allow hint bits > to be WAL-logged without checksums in 9.3. All the code is there, it'd just > be a new guc to control it separetely from checksums. On the other hand if you're going to wal log the hint bits why not enable checksums? Do we allow turning off checksums after a database is initdb'd? IIRC we can't turn it on later but I don't see why we couldn't turn them off. -- greg
В списке pgsql-hackers по дате отправления