Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jERxF-0003ER-3q for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Mar 2020 06:13:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jERxD-0002ii-P7 for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Mar 2020 06:13:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jERxD-0002hq-Dx for pgsql-hackers@lists.postgresql.org; Wed, 18 Mar 2020 06:13:23 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jERx6-0006Gd-Iy for pgsql-hackers@lists.postgresql.org; Wed, 18 Mar 2020 06:13:23 +0000 Received: by mail-lj1-x22e.google.com with SMTP id g12so25671911ljj.3 for ; Tue, 17 Mar 2020 23:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=l2/Wqp9yX6UPb+OtURIu5s81gqg3hYQXvGiiMsyaTPI=; b=Yy6JQSCwb1Pt34gUDGglY9wUjiE3akT6GgoNBxlbkVJXGcwGuLd4UjEx2SjysIKV9/ xzM3MG0FzKX5rnhk860EukElCGmX5pTRqh4K8alJx8aQ1wc3/7LR+fyQ01Pr7Ocv66Q5 80KmQn8ZpdWkv07PbUYpltcuBZ2EswfAizGBA1Ma9WKSLeDrgDPVKZBfg9tAL2DkM47o i8GytUIORg/76iRApbPQVZbR4JzSLesH3O5w3rzVoYL3z5nmwtM8mJ9BR1+hB6sYwBVC H1jQvPShE+2+hGDKQs3bkEDV8MPoSpt1mJlRuT/OFJZt5qSlu+8f5PSbjA8i62eJpmLq 50Rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=l2/Wqp9yX6UPb+OtURIu5s81gqg3hYQXvGiiMsyaTPI=; b=Fw/JU5UIzkg2yByn1eLkuh4WmB2VdFsi7PTlPKkvTbVYH5SG6d/q4H4fOQjz9PjHQ9 4XCUqplFXZWDrD27mGlPgR4wiBlAUYMHYkBlrEOnxCaVCOM0+7soZxzD6ri0+0myn75O u1DtvrqoEp1Yr+25LU3rum6w4n+xb76WY0eVbWcAvNlNr9yPjRT01OSWPP2dLy9uVzvF 1XRho0MzSAqb7w4/zcnPRwbArtHvqritXB0JhdhVOvwZiQd+Fix4EnFAv9c+wZlafBFC /C4dtqm0xqyIuy9ioEBWUGKIhw67t3RiTyBXBXWRJLQ3MWNgyOtRNLZq7AD96RqKPCFS UICw== X-Gm-Message-State: ANhLgQ0fJj+uvbpi/eNRrJT7GVnK1XpFaxK3MGi+fWsc2WOaMBmejM1J qfeJTO66SrOchkZMQfBIcbo= X-Google-Smtp-Source: ADFU+vul7Ictu/KZjSMCXpwJvuCjsl23F7EsUZchK2ZzD5ejMJDZGfwAHozMDBRJXGGupvKTj5ddHQ== X-Received: by 2002:a05:651c:445:: with SMTP id g5mr1344773ljg.125.1584511995659; Tue, 17 Mar 2020 23:13:15 -0700 (PDT) Received: from nol (82-64-124-11.subs.proxad.net. [82.64.124.11]) by smtp.gmail.com with ESMTPSA id u6sm3996756lff.35.2020.03.17.23.13.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Mar 2020 23:13:15 -0700 (PDT) Date: Wed, 18 Mar 2020 07:13:12 +0100 From: Julien Rouhaud To: Michael Paquier Cc: Robert Haas , PostgreSQL Hackers , Masahiko Sawada Subject: Re: Online checksums verification in the backend Message-ID: <20200318061312.GB58497@nol> References: <20191210022633.GD72921@paquier.xyz> <20200311071823.GA4643@nol> <20200316030638.GA2331@paquier.xyz> <20200316082122.3wr4swqvpe7j5cg5@nol> <20200318042047.GH214947@paquier.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200318042047.GH214947@paquier.xyz> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Mar 18, 2020 at 01:20:47PM +0900, Michael Paquier wrote: > On Mon, Mar 16, 2020 at 09:21:22AM +0100, Julien Rouhaud wrote: > > On Mon, Mar 16, 2020 at 12:29:28PM +0900, Michael Paquier wrote: > >> Based on the feedback gathered on this thread, I guess that you should > >> have a SRF returning the list of broken blocks, as well as NOTICE > >> messages. > > > > The current patch has an SRF and a WARNING message, do you want an additional > > NOTICE message or downgrade the existing one? > > Right, not sure which one is better, for zero_damaged_pages a WARNING > is used. Sorry forgot to answer that. IMHO a WARNING is better here, as we're talking about data corruption. Also, a WARNING will be reported to both the client and server logs, which sounds like a good thing.