On 24/01/17 02:39, Michael Paquier wrote: > On Tue, Jan 24, 2017 at 10:26 AM, Stephen Frost <sfr...@snowman.net> wrote: >> * Tom Lane (t...@sss.pgh.pa.us) wrote: >>>>> I don't recall ever seeing a checksum failure on a Heroku Postgres >>>>> database, >> >> Not sure how this part of that sentence was missed: >> >> ----- >> ... even though they were enabled as soon as the feature became >> available. >> ----- >> >> Which would seem to me to say "the code's been running for a long time >> on a *lot* of systems without throwing a false positive or surfacing a >> bug." > > I am reading that similarly to what Tom is seeing: enabling it has > proved Heroku that it did not catch problems in years, meaning that > the performance cost induced by enabling it has paid nothing in > practive, except the insurance to catch up problems should they > happen. >
+1 -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
