Re: silence compiler warning in brin.c
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Zhihong Yu <zyu@yugabyte.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2022-06-01T21:30:13Z
Lists: pgsql-hackers
On Wed, Jun 01, 2022 at 05:08:03PM -0400, Tom Lane wrote:
> Hmm, if we're following amcheck's example it should be more like this:
>
> diff --git a/src/backend/access/brin/brin.c b/src/backend/access/brin/brin.c
> index 52f171772d..0de1441dc6 100644
> --- a/src/backend/access/brin/brin.c
> +++ b/src/backend/access/brin/brin.c
> @@ -1051,7 +1051,13 @@ brin_summarize_range(PG_FUNCTION_ARGS)
> save_nestlevel = NewGUCNestLevel();
> }
> else
> + {
> heapRel = NULL;
> + /* Set these just to suppress "uninitialized variable" warnings */
> + save_userid = InvalidOid;
> + save_sec_context = -1;
> + save_nestlevel = -1;
> + }
>
> indexRel = index_open(indexoid, ShareUpdateExclusiveLock);
>
> I like this better anyway since the fact that the other two variables
> aren't warned about seems like an implementation artifact.
Yeah, that is better. It's not clear why the other variables aren't
subject to the same warnings, so we might as well cover our bases.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
Commits
-
Silence compiler warnings from some older compilers.
- dd672be38d39 12.12 landed
- dd1c8dd1015f 15.0 landed
- c05118014776 10.22 landed
- 60ca2e8418a1 13.8 landed
- 4e467261560f 14.4 landed
- 37290f7f5a9a 11.17 landed