From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Michael Banck <michael(dot)banck(at)credativ(dot)de> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) |
Date: | 2021-01-06 01:52:53 |
Message-ID: | X/UX9WO4ueC7AleI@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 04, 2021 at 07:11:43PM +0100, Michael Banck wrote:
> Am Samstag, den 02.01.2021, 10:47 -0500 schrieb Stephen Frost:
>> * Michael Paquier (michael(at)paquier(dot)xyz) wrote:
>>> On Fri, Jan 01, 2021 at 08:34:34PM +0100, Michael Banck wrote:
>>> > I think enough people use data checksums these days that it warrants to
>>> > be moved into the "normal part", like in the attached.
>>>
>>> +1. Let's see first what others think about this change.
>>
>> I agree with this.
Okay, so I have applied this part as it makes sense independently.
>> But I'd also like to propose, again, as has been
>> discussed a few times, making it the default too.
While I don't particularly disagree, I think that this needs careful
evaluation.
> So maybe we should switch on wal_compression if we enable data checksums
> by default.
I don't agree with this assumption. In some CPU-bounded workloads, I
have seen that wal_compression = on leads to performance degradation
with or without checksums enabled.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2021-01-06 02:02:29 | logical replication worker accesses catalogs in error context callback |
Previous Message | Kyotaro Horiguchi | 2021-01-06 01:48:04 | Re: A failure of standby to follow timeline switch |