Re: pgsql: Track block level checksum failures in pg_stat_database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Track block level checksum failures in pg_stat_database
Date: 2019-04-30 21:56:47
Message-ID: 27245.1556661407@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Tue, Apr 30, 2019 at 6:33 PM Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
>> It seems this commit forgot to add PgStat_MsgChecksumFailure to the
>> PgStat_Msg union.

> Oops, indeed. That's embarrassing. Trivial fix attached if that helps.

Seems like this exposes a generic weakness in the way pgstat.c is coded.
I'm inclined to adjust the switch logic in PgstatCollectorMain along
the lines of

- pgstat_recv_inquiry((PgStat_MsgInquiry *) &msg, len);
+ pgstat_recv_inquiry(&msg.msg_inquiry, len);

so that you *couldn't* forget to extend the union, as long as you
followed the existing code's style.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Julien Rouhaud 2019-04-30 22:48:58 Re: pgsql: Track block level checksum failures in pg_stat_database
Previous Message Julien Rouhaud 2019-04-30 21:41:55 Re: pgsql: Track block level checksum failures in pg_stat_database