Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbN08-00G7Iw-Q6 for pgsql-general@arkaria.postgresql.org; Tue, 06 Aug 2024 16:25:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sbN06-001HA2-5Q for pgsql-general@arkaria.postgresql.org; Tue, 06 Aug 2024 16:25:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbN05-001H9t-QO for pgsql-general@lists.postgresql.org; Tue, 06 Aug 2024 16:25:29 +0000 Received: from mail-oa1-x2c.google.com ([2001:4860:4864:20::2c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sbN03-003P8T-4F for pgsql-general@lists.postgresql.org; Tue, 06 Aug 2024 16:25:28 +0000 Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-260f033fda3so489989fac.3 for ; Tue, 06 Aug 2024 09:25:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722961526; x=1723566326; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=nuFFfhjCmtTOmihCFyPbkRG3JiAQutfInnbgfeC0Bi8=; b=bnjvTk8kDzJQiVTBgUCulf4QHEOtkTzeChgWqp8OLmVQUcjX+LyGiYZEDYrHwaiPTP docAguU9+TqmrM/LvXn+RUVlKoJfATSqW0Gg3XPyQj7rdt7TUeAD5OcXXGDyaGD8GTO1 ZWtJxExtbT+yqbh3EFF11G2ekOx+7UEDuNLUgZ627V+mYGo/F62ptG0ii3FQJOOW06Kz 4PtAdD7S0NHhRjv4n/TzoR9E64JYNTqDJMmKRLQ7XTIeOHfNOH3OhZdPqzEI2dwtvzkU Sh2EeGrsaapQblqIeSeey6VmbDJcaFxSEYKZ7TdsJguYh/oAV4Hk80EJj2FoPPyx85dB 64Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722961526; x=1723566326; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nuFFfhjCmtTOmihCFyPbkRG3JiAQutfInnbgfeC0Bi8=; b=DVWw7jQBpOwfLSJ9QFWJbQjlNNjKL09+ScsjN3/O5tj7Nuu4XszrNJSW4Phz3aoSfN qe1885E4Mbjdj/lw51Ct4z5/kRwJA8yIRAZAOtN6Ax3cXCnaHAUMBAzLtb3eMCWTK711 KDRhcqtP3tCoWFYczW8k6V4mIvjgeXDKExSbPheE+zX6vuIzQAp3UFBFa0mkiYDo8gnu 7k040EWuk5xHJVYqdhKLeioVIzwO1/u/gK3+n/flibYNyw9SQmwlGMGqnGXv+91cijtQ 1Kh54QnS+Vs6psoI9X1S1ixO4oSqwJvyog1hninU3Lii+NYnm/Oqc92UZaV2zfJEf+dD eS/w== X-Gm-Message-State: AOJu0YyXUebq1BCGkYh5klZK3w9tHKxZfUimN/F1dNh6ZieRVnE+cktG EQlZWDjZhHRcVUQuuadJJNs9OdQ+ng1GAwzk8QCqKz7lKfMHMUDTVcP0fPG/7s3dWnsETtDfeZD EgstQvOxbiy6wjsH7ZG2BLhSN5v9ylQ== X-Google-Smtp-Source: AGHT+IECDFEthHGUcJNwJYfsHNVtdaZPgTVTpRWfnAiAQLO3Iilmq6m6uyb8tY5wINlFX/EuMkO0zmH2hseppkHZW2w= X-Received: by 2002:a05:6870:a54a:b0:24f:dd11:4486 with SMTP id 586e51a60fabf-26891e92ab4mr19080096fac.36.1722961526096; Tue, 06 Aug 2024 09:25:26 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Tue, 6 Aug 2024 12:25:15 -0400 Message-ID: Subject: Re: data checksums To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000b98c01061f063daa" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b98c01061f063daa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 6, 2024 at 11:12=E2=80=AFAM bruno vieira da silva wrote: > Hello. > I've been dealing with some database corruption events, so i've been > wondering to enable data checksums on my deployments. > > so my question is why data checksums aren't enabled by default on pg? the > pg doc > mentions a considerable performance penality, how considerable it is? > I'm going to hazard a guess that the relevant line from the docs were written many many years ago, back when servers were much slower. We certainly didn't notice any speed degradation when going from PG 9.6.24 to PG 14.12. Or... we just use enough hardware and flash-only SAN disks to make the overhead minuscule. --=20 Death to America, and butter sauce. Iraq lobster! --000000000000b98c01061f063daa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Aug 6, 2024 at 11:12=E2=80=AFAM b= runo vieira da silva <brunogiovs= @gmail.com> wrote:
Hello.
I'= ;ve been dealing with some database corruption events, so i've been won= dering to enable data checksums on my deployments.=C2=A0

so my question is why data checksums aren't enabled by default o= n pg? the pg doc=C2=A0
mentions a considerable performance penali= ty, how considerable it is?
=C2=A0
=
I'm going to hazard a guess that the relevant line from the = docs were written many many years ago, back when servers were much slower.<= /div>

We certainly didn't notice any speed degradati= on when going from PG 9.6.24 to PG 14.12.=C2=A0 Or... we just use enough ha= rdware and flash-only SAN disks to make the overhead minuscule.
<= br>
--
Death to America, and butter= sauce.
Iraq lobster!
--000000000000b98c01061f063daa--