Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jic4r-0001EV-2X for pgsql-admin@arkaria.postgresql.org; Tue, 09 Jun 2020 11:05:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jic4p-00080g-S4 for pgsql-admin@arkaria.postgresql.org; Tue, 09 Jun 2020 11:05:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jic4p-00080Z-GW for pgsql-admin@lists.postgresql.org; Tue, 09 Jun 2020 11:05:55 +0000 Received: from mail-ed1-x542.google.com ([2a00:1450:4864:20::542]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jic4m-0002AF-Og for pgsql-admin@postgresql.org; Tue, 09 Jun 2020 11:05:55 +0000 Received: by mail-ed1-x542.google.com with SMTP id e12so15990692eds.2 for ; Tue, 09 Jun 2020 04:05:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=qMc2NPqo8OKroG4Y3BuRx7XR1LCNE+DhVBN3hzo+740=; b=RefLpNyUHWa7EvNLHVw3riYjluIvNKeeF2OJY+Ikl9xh4tdnkaM1p/9EzbvcC3xq9j B21FeOMT4/BdSNoRkr9Kv7Grru/7tfp8vgb/qWmYB6w1fd4oO2DNYxE8Q4KKh1WfStGz ZDl2CWraot7PpyzG5+CTPdzUJShC2cElSIHSiMnoV8/YgdwGl7tpdJbgEA7ykrMVHWsB KZ1hVuvLYRYeEB48uDfGSxSXSmuc6AXLY0DKoU1h/6nuWUgMU8Fm+20s7B3TmScBU817 RsyzjgYRaEw8Vuu9B+qS9J3jN2P0I/udoW7ELVF5dpFpdC6jshWWoOy01dy4V6KlNZ8P bwqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=qMc2NPqo8OKroG4Y3BuRx7XR1LCNE+DhVBN3hzo+740=; b=WmP9AlDHQPZj1aB3iOCcHKswDBObQI5KbUS9cDh67pUl3LJQtIEw/MGWN722XGKtdB lssjOF41Zw81J34ShFeAm3zxns2sTr1JsUAR4kbiLtj8oWvL3syF7nxFuDYnn9biUzxs gzIk8+Yms2DTt/JrUGMJC0PmHA5K4+d8jEJHmf0cvEBYaQmnwgpKqWCqD/EVUdqQ5jLN R+7rcvc6IgQsoW11SVSG0Hdb5OyF9UZ8s9pbPQs39uJldU/s4b+9UITPtEQsXifrKdPi wZYzWV1xmAtTUv9G5g8SoLyT90+S7Lghxo+KqX8iWbk2t8wLXAg7g5D7s+ynwghwvfDy rkfA== X-Gm-Message-State: AOAM532eNAGxmigI/rs1M9yUdkiSqGlwEU/kfhNEXwcRTmuOvyuGklor S46UPNd/A01N96W6O6gbW9cxRg== X-Google-Smtp-Source: ABdhPJwOBKGmBGIKlnwri+CWaE8X8HvJSTq8+bSi/UYvb+leunx+TredDS/pIhBMUEYAWrpczDte5g== X-Received: by 2002:aa7:c756:: with SMTP id c22mr26604831eds.239.1591700751809; Tue, 09 Jun 2020 04:05:51 -0700 (PDT) Received: from localhost.localdomain ([212.186.219.234]) by smtp.gmail.com with ESMTPSA id a62sm15102020edf.38.2020.06.09.04.05.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Jun 2020 04:05:51 -0700 (PDT) Message-ID: <56548c641f4c30cdc4950c00d1988f7deda36e6c.camel@cybertec.at> Subject: Re: block corruption message in error logs. From: Laurenz Albe To: vinod kale , pgsql-admin@postgresql.org Cc: vvkgadge56@gmail.com Date: Tue, 09 Jun 2020 13:05:50 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, 2020-06-09 at 07:27 +0530, vinod kale wrote: > I have dought regarding block corruption message in error logs. > Below is the scenario :- > If i made changes in table's disk level file so is it possible that it can display in postgres error logs. > If possible then what are the parameters in postgresql.conf needs to capture it. The default setting of "log_min_error_messages" will already log such errors. Of you will only get an error if an SQL statement actually tries to access the corrupted block. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com