From: | vinod kale <vinod16895(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-admin(at)postgresql(dot)org, vvkgadge56(at)gmail(dot)com |
Subject: | Re: block corruption message in error logs. |
Date: | 2020-06-09 19:17:04 |
Message-ID: | CAD7GeHQ3OKqn=hXeK1veMw4PD7h87ryUshkzOymDe3wku9D4uQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thank you for the clarification.
On Tue, 9 Jun 2020, 16:35 Laurenz Albe, <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> 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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2020-06-09 19:48:35 | Understanding JSONB and TOAST tables |
Previous Message | Laurenz Albe | 2020-06-09 11:05:50 | Re: block corruption message in error logs. |