From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Production block comparison facility |
Date: | 2014-07-20 08:31:26 |
Message-ID: | CA+U5nMLb2g0Rreatc_HJb6VDMgh9DKfnya1YkZFckptcaZXeaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The block comparison facility presented earlier by Heikki would not be
able to be used in production systems. ISTM that it would be desirable
to have something that could be used in that way.
ISTM easy to make these changes
* optionally generate a FPW for every WAL record, not just first
change after checkpoint
full_page_writes = 'always'
* when an FPW arrives, optionally run a check to see if it compares
correctly against the page already there, when running streaming
replication without a recovery target. We could skip reporting any
problems until the database is consistent
full_page_write_check = on
The above changes seem easy to implement.
With FPW compression, this would be a usable feature in production.
Comments?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2014-07-20 09:01:10 | Re: Built-in binning functions |
Previous Message | Amit Kapila | 2014-07-20 05:44:38 | Re: [bug fix] pg_ctl always uses the same event source |