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 1vDkkZ-00F3eo-RP for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Oct 2025 14:32:39 +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 1vDkkY-00DLEY-OG for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Oct 2025 14:32:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <3danissimo@gmail.com>) id 1vDkkY-00DLEQ-D0 for pgsql-hackers@lists.postgresql.org; Tue, 28 Oct 2025 14:32:37 +0000 Received: from mail-yw1-x112c.google.com ([2607:f8b0:4864:20::112c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from <3danissimo@gmail.com>) id 1vDkkU-004iJ6-2E for pgsql-hackers@postgresql.org; Tue, 28 Oct 2025 14:32:36 +0000 Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-7847f4265e3so63607587b3.3 for ; Tue, 28 Oct 2025 07:32:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761661952; x=1762266752; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vjOLPfgyFhZucSTG3mL8cYnPPs1RMdrNuAW3ToTvmVQ=; b=I32Mr13tr+k7IW8S0sxjl716WVOomgNkzNWsJ3nHDWP0jvuEovOmo1fnDwQ0ZoOOGo O9yDsnB4hfrq9WlzJHb1/1ltt/OE9kqS/X1o6PNb6rJLqVnQs/XEA2r34Oq9JiO1SJUV UXjZhziZMqk7tvYdrR0JFB2GddSFOsJhoMytuwrE7Ml9WbvKsARjFAG/pzrV7QlfchDw DpHAiMeKqZprgMAC0XQ1MGG9PoSJTTuG3irJZH121cg8PEkKpMmBXQZdHU9eu7rPg5Rs s0JCdw3+lHFt1jep/Q908iZwqsSaBWyAg+DePCrPbnAWW10djAeiTIjtsT2yCHxEOUDl 5HHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761661952; x=1762266752; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vjOLPfgyFhZucSTG3mL8cYnPPs1RMdrNuAW3ToTvmVQ=; b=FwBFc/+hhJuwinIQdMx6TCKEVTbZ0yPtN2t/bzAl5b6mUgQW27rxOXpos0obyOL7bM PuJ4hIbiJ0gCmF8MkzPxWUJk+iiyHGLjRClShv7hY6nGBbmddoelp98QvWe0QUzx61Pl 9fMmUDtkaZS7CWU1rHaR5Q+INaMqDf+NnaZ3eF7rD+t0R+UvPbIC+AIe8qiI99d4LUon Ax/2jAOHBnc5kmqaXdiRHPutYsv2ZgUZ/EkvtWI/TWtfPZ8m8bD3iIaEO9ayYI0vRQP2 M3GDxrhAqpcxs2yzlspp+qEOmbwLcI/ZUNlA6FDZYMHVLk7G0nU/zhHsyop6wwHujqBB 80Cw== X-Forwarded-Encrypted: i=1; AJvYcCVXG2mClIeXmNT+reztMvQneTKXXlJaCNbOW2ZcsdzzMbiyozEg5gPMc6lurvJXzyYydjfeQ/WcxQN/BAza@postgresql.org X-Gm-Message-State: AOJu0Yx12E/MHaiQr+TP+o0x13RQuBDwiEmylQVDpAFS4jL8EUwmyPWh suhdC4W4BAyB9A7YK73cLyWCDT221Fa72GXF26k5Ord3BELuQAPa9F5JYc1OpL1CEEwg3kk6tQd nDT4XyHaMdA1vS+r8XXcQV/ixYP2tkP8= X-Gm-Gg: ASbGnctFar8/IcHnMyl9whr9i0c0QJRdFeiH1UAt7FIQAZlCA/yZIZN/OMKleHAjUC8 bBh5WEJHF9JkvIocRTMe4LhcbS6vPDM8tc1cd6s1CoZXTo8CSiRpL5+B80K2XvGfT1PHDHIrb2X nVWHYvb5Ptd2ahqkFK0iUtrjIJjSgMcmWAV8d3Dhru5CqLo/MG/Vh5oROnCevP869QesMHdVx5f j5Liheb6NC4OPhEydXnZBcluBXdaaLBfkZmYhoOcpz+6nicwsChYkCL3ANaWSc= X-Google-Smtp-Source: AGHT+IGCPZIybN1rcjNdL7xG9CuDAJcYgdqBB1YTIqTIDHIrGNf53WYX3L1Y1jBBLmrgS+tjFBTFgeAEWUNJ6lraNlg= X-Received: by 2002:a53:8402:0:b0:63f:2bc7:7074 with SMTP id 956f58d0204a3-63f6ba38705mr2453553d50.60.1761661950890; Tue, 28 Oct 2025 07:32:30 -0700 (PDT) MIME-Version: 1.0 References: <68f3771f-91f5-4cb7-b1de-74d9abbf0b96@vondra.me> In-Reply-To: From: Daniil Davydov <3danissimo@gmail.com> Date: Tue, 28 Oct 2025 21:32:19 +0700 X-Gm-Features: AWmQ_blKvvoa13BIy1M1FBz0Q2iolselsBUktjU4R6uKY42nLHvK7_BZs1NEUHI Message-ID: Subject: Re: Batching in executor To: Amit Langote Cc: Tomas Vondra , PostgreSQL-development Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, As far as I understand, this work partially overlaps with what we did in the thread [1] (in short - we introduce support for batching within the ModifyTable node). Am I correct? It's worth saying that the patch in that thread is already quite old - now I have an improved implementation and tests for it (as well as performance measurements). But the basic idea and design remained unchanged. Maybe we can combine approaches? I haven't reviewed patches in this thread yet, but I'll try to do it in the near future. [1] https://www.postgresql.org/message-id/flat/CALj2ACVi9eTRYR%3Dgdca5wxtj3Kk_9q9qVccxsS1hngTGOCjPwQ%40mail.gmail.com -- Best regards, Daniil Davydov