Re: Definitional issue: stddev_pop (and related) for 1 input

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Definitional issue: stddev_pop (and related) for 1 input
Date: 2020-06-13 15:56:00
Message-ID: 831663.1592063760@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-06-13 16:17:40 Uninitialized-variable warnings in nbtinsert.c
Previous Message Bruce Momjian 2020-06-13 12:46:36 Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0