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 1r59YD-00C3AR-Ra for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Nov 2023 19:03:17 +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 1r59YA-009lfc-GP for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Nov 2023 19:03:14 +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 1r59Y9-009lfU-T8 for pgsql-hackers@lists.postgresql.org; Mon, 20 Nov 2023 19:03:14 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r59Y3-006WHE-4S for pgsql-hackers@postgresql.org; Mon, 20 Nov 2023 19:03:12 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 85E453200BEA; Mon, 20 Nov 2023 14:03:04 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 20 Nov 2023 14:03:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1700506984; x= 1700593384; bh=8CFyJZ3PpRiZoCN0ydNpSsmJRBGn/QgIOIowMXhM/DQ=; b=o CepO4w+9fiEf4Ak/DkoPM6/for00N4tljliLHsLqCKteRiq2PIkjQmjI8fThCKOh 62GxQ7Dg1LGvFsqjtcV0Q7VXTFfSm76NldVwrJfhyjWl9yR82q4ZkaFmjcOdwBfU yG5Woa9we8hd7+Eb/DmVifJKLkBwBWXmM3MHEw3hQtyKSm4Maj8gK+QjVO1xFfJO EhsNHeb6YVMfnEb41EN5D5iop9meqArX9gvou6sa4TeJtgVECTNkvek8pVT3UqJE Jr7cMIvhGCkuzOGVRs6EtM8h8Xk6g5Aty0GcYZAx7A4gceW72XS9ThVWvoCm5MKm gw/2D5s05CJpTx9spX9fA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudegjedgleefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Nov 2023 14:03:03 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1700506981; bh=bbJNVxh+0w8cct1/jjMBCOGABOTZrO9kgHam44FFgzk=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=PqNg35lDHNL/uvuTN5Y5oIAScxxIgDeLpJOee6KXgC8rcaMUxZKmpFaiMvY3tAnAD TjCuIUOF55pmatshqPOOx3l758DtLk4B3zBNUkPA+CK8slLBw3q/9OZKeU2FmKrtoI JiEDNQMIIRvw4T4DT04t/Pfy+7i8Mor4Pjh1hvr0+qgqTkpeVNhJ4sNX49cWi6T53c chM2X/8GFR6ZS/RzCSN5Ni3uwufXM4cPkg5ZlBPWlLT1ihnG0NAYlDMt5/Eqn1GgCl p1U5+GLfkyXQi+0AiXmM/mDmo5C3oUDVzaHNqQdMkp+bUa5m4rOxDS/+KNiGvl75wK mMWbr7h39XrlA== Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id C725D127; Mon, 20 Nov 2023 20:03:01 +0100 (CET) Date: Mon, 20 Nov 2023 20:03:01 +0100 From: Alvaro Herrera To: Robert Haas Cc: Dilip Kumar , Andres Freund , "pgsql-hackers@postgresql.org" Subject: Re: trying again to get incremental backup Message-ID: <202311201903.j3r4qidaxtkc@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Nov-16, Robert Haas wrote: > On Thu, Nov 16, 2023 at 12:23 PM Alvaro Herrera wrote: > > I don't understand this point. Currently, the protocol is that > > UPLOAD_MANIFEST is used to send the manifest prior to requesting the > > backup. You seem to be saying that you're thinking of removing support > > for UPLOAD_MANIFEST and instead just give the LSN as an option to the > > BASE_BACKUP command? > > I don't think I'd want to do exactly that, because then you could only > send one LSN, and I do think we want to send a set of LSN ranges with > the corresponding TLI for each. I was thinking about dumping > UPLOAD_MANIFEST and instead having a command like: > > INCREMENTAL_WAL_RANGE 1 2/462AC48 2/462C698 > > The client would execute this command one or more times before > starting an incremental backup. That sounds good to me. Not having to parse the manifest server-side sounds like a win, as does saving the transfer, for the cases where the manifest is large. Is this meant to support multiple timelines each with non-overlapping adjacent ranges, rather than multiple non-adjacent ranges? Do I have it right that you want to rewrite this bit before considering this ready to commit? -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "No nos atrevemos a muchas cosas porque son difíciles, pero son difíciles porque no nos atrevemos a hacerlas" (Séneca)