| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Checksums by default? |
| Date: | 2017-01-21 16:41:45 |
| Message-ID: | fefd05e8-26e3-5453-2c51-c56b67326629@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/21/2017 04:48 PM, Stephen Frost wrote:
> * Fujii Masao (masao(dot)fujii(at)gmail(dot)com) wrote:
>> If the performance overhead by the checksums is really negligible,
>> we may be able to get rid of wal_log_hints parameter, as well.
>
> Prior benchmarks showed it to be on the order of a few percent, as I
> recall, so I'm not sure that we can say it's negligible (and that's not
> why Magnus was proposing changing the default).
It might be worth looking into using the CRC CPU instruction to reduce
this overhead, like we do for the WAL checksums. Since that is a
different algorithm it would be a compatibility break and we would need
to support the old algorithm for upgraded clusters..
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-01-21 16:41:56 | Re: Checksums by default? |
| Previous Message | Petr Jelinek | 2017-01-21 16:39:29 | Re: Checksums by default? |