Re: Definitional issue: stddev_pop (and related) for 1 input - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Definitional issue: stddev_pop (and related) for 1 input
Date
Msg-id 831663.1592063760@sss.pgh.pa.us
Whole thread Raw
In response to Re: Definitional issue: stddev_pop (and related) for 1 input  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> The patch looks reasonable, except I wonder if all compilers are smart
> enough to realise that totCount is always initialised.

I think they should be, since that if-block ends with a return;
the only way to get to the use of totCount is for both parts of the
first if-condition to be executed.

In any case, we do have an effective policy of ignoring
uninitialized-variable warnings from very old/stupid compilers.
locust and prairiedog, which I think use the same ancient gcc
version, emit a couple dozen such warnings.  If they are the only
ones that complain about this new code, I'll not worry.

Thanks for looking at the patch!

            regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0
Next
From: Tom Lane
Date:
Subject: Uninitialized-variable warnings in nbtinsert.c