postgres/timescaledb
1
0
Fork 0
mirror of https://github.com/timescale/timescaledb.git synced 2025-05-26 00:00:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

Initialize variables complained about by older compilers

Browse Source 
GCC 7.5 warns that invalidation_range in continuous aggregate
materialization may be used uninitialized.
Older clang versons warn that res in calculate_next_start_on_failure
may be used uninitialized.
This patch changes the code to always initialize those two variables.
This commit is contained in:
Sven Klemm 2020-06-08 19:58:35 +02:00 committed by Sven Klemm
parent d3ed288d2a
commit 5bbab82eca
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/bgw/job_stat.c
View File

@ -195,7 +195,7 @@ calculate_next_start_on_failure(TimestampTz finish_time, int consecutive_failure
{
float8 jitter = calculate_jitter_percent();
/* consecutive failures includes this failure */
TimestampTz res;
TimestampTz res = 0;
volatile bool res_set = false;
TimestampTz last_finish = finish_time;
float8 multiplier = (consecutive_failures > MAX_FAILURES_MULTIPLIER ? MAX_FAILURES_MULTIPLIER :

2
tsl/src/continuous_aggs/materialize.c
View File

@ -692,7 +692,7 @@ materialization_invalidation_log_get_range(int32 materialization_id, Oid type, i
int64 invalidate_prior_to_time)
{
bool found = false;
InternalTimeRange invalidation_range;
InternalTimeRange invalidation_range = { 0 };
ScanIterator iterator =
ts_scan_iterator_create(CONTINUOUS_AGGS_MATERIALIZATION_INVALIDATION_LOG,
AccessShareLock,