Thread: pgsql: Initialize HASHCTL differently, to suppress Coverity warning

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.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f011e82c2c886329245f821146c560a3607f7aba

Modified Files
--------------
src/backend/access/transam/xlogprefetcher.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)

Heikki Linnakangas <heikki.linnakangas@iki.fi> writes:
> Initialize HASHCTL differently, to suppress Coverity warning

koel says this is mis-indented.

            regards, tom lane