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 1u4Nap-001Jvt-Vh for pgsql-hackers@arkaria.postgresql.org; Mon, 14 Apr 2025 17:27:36 +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 1u4Nao-003rBl-7X for pgsql-hackers@arkaria.postgresql.org; Mon, 14 Apr 2025 17:27:35 +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 1u4Nan-003rBa-Tu for pgsql-hackers@lists.postgresql.org; Mon, 14 Apr 2025 17:27:34 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u4Nam-0003XN-0Y for pgsql-hackers@lists.postgresql.org; Mon, 14 Apr 2025 17:27:33 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 53EHRTWS1282068; Mon, 14 Apr 2025 13:27:29 -0400 From: Tom Lane To: Dimitrios Apostolou cc: pgsql-hackers@lists.postgresql.org, Nathan Bossart Subject: Re: [PING] [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward In-reply-to: References: <2edb7a57-b225-3b23-a680-62ba90658fec@gmx.net> Comments: In-reply-to Dimitrios Apostolou message dated "Mon, 14 Apr 2025 18:31:48 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1282066.1744651649.1@sss.pgh.pa.us> Date: Mon, 14 Apr 2025 13:27:29 -0400 Message-ID: <1282067.1744651649@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Dimitrios Apostolou writes: > Any feedback on this one-liner? Or is the lack of feedback a clue that I > have been missing something important in my patch submission? :-) The calendar ;-). At this point we're in feature freeze for v18, so things that aren't bugs aren't likely to get much attention until v19 development opens up (in July, unless things are really going badly with v18). You should add your patch to the July commitfest [1] to make sure we don't lose track of it. regards, tom lane [1] https://commitfest.postgresql.org/53/