From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [87.239.111.99] (localhost [127.0.0.1]) by dev.tarantool.org (Postfix) with ESMTP id 787C36EC55; Mon, 3 May 2021 23:37:57 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 787C36EC55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1620074277; bh=inNAsydttZZttECgNEhtpi8HGjVi8vsY4/U0743RS6g=; h=Date:To:Cc:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=thf11gT/fm7NI7cMoRjp0SlqLgjeO3KQmUTFZi2pzQxkAicJ0brn8SKZk/sqU+0KG b4tDe/2xBgSOUBV9nMWswDs/p7414kt7E2PWTXEW3cuiPMUsfuSip0U3gHOHhq0v8y n8han3O0d1sMC9aeojkj8/D3yLs/JVTPCkC613lE= Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 24B5C6EC55 for ; Mon, 3 May 2021 23:37:57 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 24B5C6EC55 Received: by mail-lj1-f171.google.com with SMTP id l22so8442415ljc.9 for ; Mon, 03 May 2021 13:37:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=DR0sC/vGTEAmU+1Y3A8PqleB73p//Iur1skh2gtsf7Y=; b=ibTg5b9nn3YHBMnuE5NECFq1leJUqmb+A8t0UiCcLND6CsyVYLo0wFHftPjQlizHBT oyfZ3q9mjTC0OKKloSkHVcO77A1lfFr1ISrrYyD8Yfo5uq3g9gclzRDuNsF4ncmZFv8M Jud2laMTafHtE6NMz8q69DaFMVV1VvV3YBhiQG16v6aYVYfdmshS6dd216c8nXPb8xsU 7idNSmb+BZxmkQ0QI8ramrf85NGaZDLJDC3HC69rjjv74Cd9+kbFc1AQ8xJppWx57kza LTRo5P2uJAQtEbjYy4p0t3p9PcZ87WZuZ9slY4frU2t16IB0gB/0GtTQVvMKTEBKnPmj jXmA== X-Gm-Message-State: AOAM531gprcFON4T4twlPNsakUdlreaO3xg6MhEevC7y6U+7xt9sibYd 3uYfhRRzvK8ymuGOFqQzRw== X-Google-Smtp-Source: ABdhPJycnbYExcpyvHp1EScTsLUJbaMvrKvINdktF3x+DNqrggvf6sBdh91aQ9fxLLVdIDvdTlj61Q== X-Received: by 2002:a2e:8511:: with SMTP id j17mr3281206lji.415.1620074276782; Mon, 03 May 2021 13:37:56 -0700 (PDT) Received: from sterling.local ([46.188.68.12]) by smtp.gmail.com with ESMTPSA id c11sm1409257ljr.70.2021.05.03.13.37.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 May 2021 13:37:56 -0700 (PDT) Received: by sterling.local (Postfix, from userid 1000) id A79A3E60076; Mon, 3 May 2021 23:37:55 +0300 (MSK) Date: Mon, 3 May 2021 23:37:55 +0300 To: Cyrill Gorcunov Cc: tml , Mons Anderson , Vladislav Shpilevoy Message-ID: <20210503203755.GA11759@starling> Mail-Followup-To: Konstantin Osipov , Cyrill Gorcunov , tml , Mons Anderson , Vladislav Shpilevoy References: <20210430153940.121271-1-gorcunov@gmail.com> <20210430153940.121271-2-gorcunov@gmail.com> <20210503202109.GA6976@starling> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [RFC v3 1/3] xrow: allow to pass timestamp via xrow_encode_vclock_timed helper X-BeenThere: tarantool-patches@dev.tarantool.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Konstantin Osipov via Tarantool-patches Reply-To: Konstantin Osipov Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" * Cyrill Gorcunov [21/05/03 23:35]: > On Mon, May 03, 2021 at 11:21:09PM +0300, Konstantin Osipov wrote: > > * Cyrill Gorcunov via Tarantool-patches [21/04/30 18:43]: > > > We will enhance applier writer with timestamp of last written row. > > > It is needed to detect downstream lag. > > > > LSN is already 64 bit and can very well fit a timestamp within a > > very reasonable range (e.g nanosecond resolution, timeuuid range). > > > > I think you shouldn't add a new field, just change the way LSN is > > generated. > > Kostya, I fear I don't get it. Currently we send back current > vclock and in the header we have the "tm" field which has been > unused before this patch. Now we start using it by sending > timestamp there. Which exactly LSN you propose to change? OK, I didn't get it, I think it's ok to fill it in then. The idea I had in mind is that all LSN become timestamps. -- Konstantin Osipov, Moscow, Russia