pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Alexander Lakhin <exclusion@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: Dilip Kumar <dilipbalaut@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: trying again to get incremental backup
Date: Fri, 22 Dec 2023 08:00:00 +0300
Message-ID: <8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com> (raw )
In-Reply-To: <CA+TgmoZetdarddiiw6CFW5UPUXuRMqaGRHRSiqRiKhmaqgE==Q@mail.gmail.com >
References: <CA+TgmoYiPn7GE_GFvGf+150XOt-Pkdm8h4rzy42jYCRrceUWhg@mail.gmail.com >
<CA+Tgmob4VFT6CuVaxwO0JjLrmCoHF+NNm_f1LsCeSi5i82MeSA@mail.gmail.com >
<CAKZiRmy73EKi3i5mdtcjn6r6WWQfKuri3HSQ+Pmdu_7g5Ef5kA@mail.gmail.com >
<CA+TgmoYUhrgcNin=qrY+J+S-f6kctf9DaUKoaD-e3cww_ox9vg@mail.gmail.com >
<CAKZiRmygUFo5Fa4y9cUwuhZNEJpP6Ng8AwbQDkYGuRAmK23zvg@mail.gmail.com >
<CA+TgmobPUXTfGC-2BTGAu5tOQQV_4x0HdOw_6o__rC0+X+1Yzw@mail.gmail.com >
<CAKZiRmwd3KTNMQhm9Bv4oR_1uMehXroO6kGyJQkiw9DfM8cMwQ@mail.gmail.com >
<CA+TgmoaGeZ=vWDYvWtPY-sP+6594HqLScvPMSSunyuYZVSWMpw@mail.gmail.com >
<CAKZiRmwTF8mj24f92mh+fiGiceO+myX6CnuYo6u2EJ+ok+Hy4Q@mail.gmail.com >
<CA+Tgmoar8+V1ycDPgT_-d+1pG_9uRn=qSPty2Y2PgNQBTqRsfQ@mail.gmail.com >
<061cccf7-0cac-804f-4c2a-9d6da8e3848b@gmail.com >
<CA+TgmobdU8Xa3bsU7F==U0vAS1KfkgvAnskjnSqagUB2gGFrcw@mail.gmail.com >
<f08f7c60-1ad3-0b57-d580-54b11f07cddf@gmail.com >
<CA+TgmoZetdarddiiw6CFW5UPUXuRMqaGRHRSiqRiKhmaqgE==Q@mail.gmail.com >
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
view thread (106+ messages) latest in thread
Message-ID: <8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com>
Permalink: ../8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com/
Also on: postgresql.org/message-id/8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: exclusion@gmail.com, robertmhaas@gmail.com, jakub.wartak@enterprisedb.com, alvherre@alvh.no-ip.org, andres@anarazel.de, peter@eisentraut.org, dilipbalaut@gmail.com
Subject: Re: trying again to get incremental backup
In-Reply-To: <8b686764-7ac1-74c3-70f9-b64685a2535f@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox