Initialize HASHCTL differently, to suppress Coverity warning
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Sun, 11 Aug 2024 17:21:16 +0000 (20:21 +0300)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Sun, 11 Aug 2024 17:21:16 +0000 (20:21 +0300)
commitf011e82c2c886329245f821146c560a3607f7aba
tree9762a9ec761c6e03fe517bc9cdd6ab5df24752d0
parentb2be5cb2ab671073ec0fc69357c3c11e25bb41cc
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.
src/backend/access/transam/xlogprefetcher.c