Initialize HASHCTL differently, to suppress Coverity warning

Heikki Linnakangas <heikki.linnakangas@iki.fi>

Commit: f011e82c2c886329245f821146c560a3607f7aba
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date: 2024-08-11T17:21:16Z
Releases: 18.0
Initialize HASHCTL differently, to suppress Coverity warning

Coverity complained that the hash_create() call might access
hash_table_ctl->hctl. That's a false alarm, hash_create() only
accesses that field when passed the HASH_SHARED_MEM flag. Try to
silence it by using a plain local variable instead of a const. That's
how the HASHCTL is initialized in all the other hash_create() calls.

Files

PathChange+/−
src/backend/access/transam/xlogprefetcher.c modified +5 −7