Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rGXdt-00FpHw-4D for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Dec 2023 05:00:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rGXdo-001pWF-IT for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Dec 2023 05:00:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rGXdo-001pW7-5H for pgsql-hackers@lists.postgresql.org; Fri, 22 Dec 2023 05:00:08 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rGXdl-00Bbrt-U7 for pgsql-hackers@postgresql.org; Fri, 22 Dec 2023 05:00:06 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-50e1112b95cso1715254e87.0 for ; Thu, 21 Dec 2023 21:00:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703221203; x=1703826003; darn=postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=o5SKivVoDY5k2nmNk7QX3OA42mCWGriwecL3FZty2fk=; b=dEr1T9SqZstluidx/TQ0bIbdkb/rUi1ojwbQHmoCykU/5JOL4f7B1U86BvuyabTkXl oaKcRBlMkPeTQax7eXDGnyqwv099ltwJbRA+fMS0e0Ew/3C+z4TJnYASjQGjjVE76wj+ vtwkS9S85TVX8J1jVO5egNZS5iYLDACf3HMje+JRKmsb+6jUgXXaKAtvdy/ISKGiFY5C +4+0YUSd4FdXQfbtFElhA964LYThkRQGd82yLhijG+ukmGthqYmgdMTjlQR27Ew0JKPe wK68dyHp4P0jx8Eo605vuIcgFPdq/WMw7hwHpYNHp45Z8XVj7aU8yC1O8D7556fHnnQn kVzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703221203; x=1703826003; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=o5SKivVoDY5k2nmNk7QX3OA42mCWGriwecL3FZty2fk=; b=B7cGftWiut7lsOjMOphIlp74slV6+8jF8261bPTmIX33gT/nO1rdV15BzpPR6GRKG9 qnZSwShmlxEKQouSmiow3yEIjz9asohBVzpJD+uw4wghG91We8OVAYRQ9e1iTM8kkhCK W20nIeDAcOWZvzUtbxQhM7KWwemMrcVZJGdsp6ozW4Ftbz+TPibstttDyYrkz3Q9fMSm aBhF0NGc7DF6oTMDlHMqfPEJcIQHyfCkQHOUWBgGRBr96LfB9JAhar+pXYLIZdX0A4qV wZnge3Nn0X1NGBkxbaMqLeDW+TLziTOmEkcVN782pW7/ubacwzEuMSfeQ6tHYpO96cVi YS8A== X-Gm-Message-State: AOJu0YxheqTY2SkXYtlmPD1KtbFlp1dBE+qCoUMDBtcMVFwT24f9eajz z7hhlalHeWiD5BA/ZAI5jNc= X-Google-Smtp-Source: AGHT+IEnUD1yNOvShvPONrw2D4c2ygRKa3rm6qd4QpQEjp9zxSa00HmF3d4H5/6G2hvZe7hA//KRZg== X-Received: by 2002:a19:6549:0:b0:50e:39a6:2c2f with SMTP id c9-20020a196549000000b0050e39a62c2fmr196502lfj.86.1703221202886; Thu, 21 Dec 2023 21:00:02 -0800 (PST) Received: from [1.0.0.7] ([178.155.20.121]) by smtp.gmail.com with ESMTPSA id c8-20020a056512238800b0050e603457eesm339961lfv.36.2023.12.21.21.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 21 Dec 2023 21:00:02 -0800 (PST) Message-ID: <8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com> Date: Fri, 22 Dec 2023 08:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: trying again to get incremental backup Content-Language: en-US To: Robert Haas Cc: Jakub Wartak , Alvaro Herrera , Andres Freund , Peter Eisentraut , Dilip Kumar , "pgsql-hackers@postgresql.org" References: <061cccf7-0cac-804f-4c2a-9d6da8e3848b@gmail.com> From: Alexander Lakhin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 21.12.2023 23:43, Robert Haas wrote: >> There are also two deadcode.DeadStores complaints from clang. First one is >> about: >> /* >> * Align the wait time to prevent drift. This doesn't really matter, >> * but we'd like the warnings about how long we've been waiting to say >> * 10 seconds, 20 seconds, 30 seconds, 40 seconds ... without ever >> * drifting to something that is not a multiple of ten. >> */ >> timeout_in_ms -= >> TimestampDifferenceMilliseconds(current_time, initial_time) % >> timeout_in_ms; >> It looks like this timeout is really not used. > Oops. It should be. See attached. My quick experiment shows that that TimestampDifferenceMilliseconds call always returns zero, due to it's arguments swapped. The other changes look good to me. Thank you! Best regards, Alexander