From: Laurenz Albe <laurenz.albe@cybertec.at>
To: vinod kale <vinod16895@gmail.com>
To: pgsql-admin@postgresql.org
Cc: vvkgadge56@gmail.com
Subject: Re: block corruption message in error logs.
Date: Tue, 09 Jun 2020 13:05:50 +0200
Message-ID: <56548c641f4c30cdc4950c00d1988f7deda36e6c.camel@cybertec.at> (raw)
In-Reply-To: <CAD7GeHQQ+YwcwbbOE=36m6QxB_gwi7FEasGt3UxNsrqmst23uQ@mail.gmail.com>
References: <CAD7GeHQQ+YwcwbbOE=36m6QxB_gwi7FEasGt3UxNsrqmst23uQ@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, vinod16895@gmail.com, vvkgadge56@gmail.com
Subject: Re: block corruption message in error logs.
In-Reply-To: <56548c641f4c30cdc4950c00d1988f7deda36e6c.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox