pgsql: Fix union for pgstat message types

Started by Magnus Haganderabout 7 years ago5 messagescomitters
Jump to latest
#1Magnus Hagander
magnus@hagander.net

Fix union for pgstat message types

The message type for temp files and for checksum failures were missing
from the union. Due to the coding style used there was no compiler error
when this happend. So change the code to actively use the union thereby
producing a compiler error if the same mistake happens again, suggested
by Tom Lane.

Author: Julien Rouhaud
Reported-By: Tomas Vondra
Discussion: /messages/by-id/20190430163328.zd4rrlnbvgaqlcdz@development

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/659e53498c3c04e4f400323c02bef98fe8d13ec8

Modified Files
--------------
src/backend/postmaster/pgstat.c | 41 ++++++++++++++++++++++-------------------
src/include/pgstat.h | 4 +++-
2 files changed, 25 insertions(+), 20 deletions(-)

#2Tomas Vondra
tomas.vondra@2ndquadrant.com
In reply to: Magnus Hagander (#1)
Re: pgsql: Fix union for pgstat message types

On Wed, May 01, 2019 at 10:34:52AM +0000, Magnus Hagander wrote:

Fix union for pgstat message types

The message type for temp files and for checksum failures were missing
from the union. Due to the coding style used there was no compiler error
when this happend. So change the code to actively use the union thereby
producing a compiler error if the same mistake happens again, suggested
by Tom Lane.

Should the tempfile bit be backported? That message was added in 9.2.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Tomas Vondra (#2)
Re: pgsql: Fix union for pgstat message types

Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:

On Wed, May 01, 2019 at 10:34:52AM +0000, Magnus Hagander wrote:

Fix union for pgstat message types

Should the tempfile bit be backported? That message was added in 9.2.

It's just cosmetic I think. The main point of having everything in
the union is to make sure the union's size/alignment are sufficient,
but the tempfile message isn't anywhere near creating an issue there.

regards, tom lane

#4Magnus Hagander
magnus@hagander.net
In reply to: Tom Lane (#3)
Re: pgsql: Fix union for pgstat message types

On Sat, May 4, 2019 at 5:54 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:

On Wed, May 01, 2019 at 10:34:52AM +0000, Magnus Hagander wrote:

Fix union for pgstat message types

Should the tempfile bit be backported? That message was added in 9.2.

It's just cosmetic I think. The main point of having everything in
the union is to make sure the union's size/alignment are sufficient,
but the tempfile message isn't anywhere near creating an issue there.

That was my thought as well. It's really only needed when we add new
things, to make sure we don't make those mistakes again. And nobody should
be adding new pgstat messages in old branches.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/&gt;
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/&gt;

#5Tomas Vondra
tomas.vondra@2ndquadrant.com
In reply to: Magnus Hagander (#4)
Re: pgsql: Fix union for pgstat message types

On Sat, May 04, 2019 at 07:08:10PM +0200, Magnus Hagander wrote:

On Sat, May 4, 2019 at 5:54 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:

On Wed, May 01, 2019 at 10:34:52AM +0000, Magnus Hagander wrote:

Fix union for pgstat message types

Should the tempfile bit be backported? That message was added in 9.2.

It's just cosmetic I think.� The main point of having everything in
the union is to make sure the union's size/alignment are sufficient,
but the tempfile message isn't anywhere near creating an issue there.

That was my thought as well. It's really only needed when we add new
things, to make sure we don't make those mistakes again. And nobody should
be adding new pgstat messages in old branches.�

Fine with me, I don't think the backbranches are broken. OTOH it's a
minor change that would make the code more similar.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services