| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enabling Checksums |
| Date: | 2013-03-04 07:11:36 |
| Message-ID: | CA+U5nMKD2DGfyF2xvNN01eGgd9_SsM_k=4akPkv13gJ90Orm_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3 March 2013 18:24, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> The 16-bit checksum feature seems functional, with two sources of overhead.
> There's some CPU time burned to compute checksums when pages enter the
> system. And there's extra overhead for WAL logging hint bits. I'll
> quantify both of those better in another message.
It's crunch time. Do you and Jeff believe this patch should be
committed to Postgres core?
Are there objectors?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2013-03-04 07:34:15 | Hold all commits! |
| Previous Message | Devrim Gündüz | 2013-03-04 07:10:28 | Re: Matview patch added rewriteDefine.c.orig to the repository |