Re: trying again to get incremental backup

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: trying again to get incremental backup
Date: 2023-12-22 05:00:00
Message-ID: 8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2023-12-22 05:39:27 Re: Transaction timeout
Previous Message Junwang Zhao 2023-12-22 02:58:05 Re: Make COPY format extendable: Extract COPY TO format implementations