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 1qQslQ-001HeL-Vj for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Aug 2023 17:02:29 +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 1qQslO-008WIX-RN for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Aug 2023 17:02:28 +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 ) id 1qQslO-008WII-HM for pgsql-hackers@lists.postgresql.org; Tue, 01 Aug 2023 17:02:27 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qQslM-000Ep1-QT for pgsql-hackers@postgresql.org; Tue, 01 Aug 2023 17:02:27 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-1bb590d5cc0so3610181fac.1 for ; Tue, 01 Aug 2023 10:02:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timescale.com; s=google; t=1690909343; x=1691514143; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=+BqzIVkKtfoglytLHQBAyD5NJidfH0mvkEpAJjrop8I=; b=TdcPNTTX9qnXpsOmSNAy2O88FfTP8NWi6A5LU1l4AKz2fhcT+efGwJ93rukz7yknaB mj7GSvUYe6QqT3aQuE7P0xklbNy7ZzFCGmYPS884uTwwAtvwU8kdL8OTKKzBHTMP1/OZ Rww9PxblRakSWjAfghVgMROOR0HUBYFLV9aMLr6/Jd/chuANNjOXFWQ3YPvw9elxSoxi F4KRGtSGumIXV6Nvvmk4sU/CWdK44Fjzqgh6Dd9xYRF5innanoYmIZJlTlkkOHvWu3nf q5FOUHwcaT3NKnT1IMY6/fCfC5FHwK18szQJYhWYduUT8muYqdN6EOxRx4QID+7rNpX6 feaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690909343; x=1691514143; h=content-transfer-encoding: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=+BqzIVkKtfoglytLHQBAyD5NJidfH0mvkEpAJjrop8I=; b=CoONedyxSp4s6gaIvRZbbmN4n4LjrdxREE80zrd0BLfSlBWTJAz1ixVyrOu3iFoNXV VzyuTQ78qLAQH6VJlnnKxRE8oLagCGo2RvPQcwrOASfdRgyz77m/XBAEOruijxC/hvwX 9STg6IjWiYFktdaEgaIeg3nwOLUPs71bBMnKrYJpiix7XlfZ9pYnzt4Z3M3kdR9gQLbK 4Y86k1qnukhlYV67hyZaoHaEVgEarQsRoa//oA1FLaXYuWsTeO6yUBP4bwOdAJwPdYuQ q+60YY/lZk6IXIpRaQbJ3auo29nfVJLf2h4kE5foiIUFRnYgudnRZvMj47Cvw1gCPrRb tC/g== X-Gm-Message-State: ABy/qLYNdoo5Wzd/ovmmXzsLng9L+7yPTMJMIQqdJK9Os+vcvhgUDQb4 KonBSzihnIAHE0Le+00QBhGnqp6fzFA9adj83LnhMA== X-Google-Smtp-Source: APBJJlGbJvcBtYV2kNMPPYbH0Eo2vgTNkS4pcYgg02bDyCraX5D/DC0X/qZMPt/jEXb1jzqrhgEBBBid2G2/gQRdpW4= X-Received: by 2002:a05:6870:d7a6:b0:1b0:e98:163b with SMTP id bd38-20020a056870d7a600b001b00e98163bmr12457081oab.21.1690909343167; Tue, 01 Aug 2023 10:02:23 -0700 (PDT) MIME-Version: 1.0 References: <20230603223824.o7iyochli2dwwi7k@alap3.anarazel.de> In-Reply-To: From: Jacob Champion Date: Tue, 1 Aug 2023 10:02:12 -0700 Message-ID: Subject: Re: New Table Access Methods for Multi and Single Inserts To: Bharath Rupireddy Cc: Andres Freund , Dilip Kumar , Luc Vlaming , Justin Pryzby , PostgreSQL-development , Paul Guo , Jeff Davis , Michael Paquier , Matthias van de Meent Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Aug 1, 2023 at 9:31=E2=80=AFAM Bharath Rupireddy wrote: > Thanks. Finally, I started to spend time on this. Just curious - may > I know the discussion in/for which this patch is referenced? What was > the motive? Is it captured somewhere? It may not have been the only place, but we at least touched on it during the unconference: https://wiki.postgresql.org/wiki/PgCon_2023_Developer_Unconference#Tabl= e_AMs We discussed two related-but-separate ideas: 1) bulk/batch operations and 2) maintenance of TAM state across multiple related operations. --Jacob