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 1s7Mij-005I6Z-Td for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 22:03:35 +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 1s7Mii-008ldn-1g for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 22:03:32 +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 1s7Mih-008ldf-Mo for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2024 22:03:31 +0000 Received: from wfhigh3-smtp.messagingengine.com ([64.147.123.154]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7Mia-000Ogo-RU for pgsql-hackers@postgresql.org; Wed, 15 May 2024 22:03:30 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id 79CA6180006D; Wed, 15 May 2024 18:03:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 15 May 2024 18:03:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1715810602; x=1715897002; bh=VnXZYNniVb lqsG0ZW0WzaNpkCkkeIr3iRpZdj6t6kzU=; b=lhLftsoSI93y2oA0WDapLF0bdp cNayzNvIudgrHGmZlq3/DMZp8zNvMnrmRE5bfMRlZ1JRuv4Plh2b+7e2MGXSGgZH FbgVIR3JbF35/ojSLKD2rJ9w7QATrJCGP0D6XEoDLzmVAwfKQp1iqgcPJJ3oQkwX ySkE0NgEiaHCwTLbgjkFjv4SC3aOQNVd1hnbes9TdRswKuwk8CcV9VokHpTb/lRP 2LjFs7CjP/3uq0LNUfEhofTFXXEJyrNTWVWpTipHeFSrrlu48Ui/RDTvFxtlXJCF R0JYWWjRW7Id/UAiWmZDb5xnLnyjb3l9S2kl4ZxjoIFontsbz5k3VWjmfYeA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1715810602; x=1715897002; bh=VnXZYNniVblqsG0ZW0WzaNpkCkke Ir3iRpZdj6t6kzU=; b=XzucXDsznCZj9xfkDdnqMDJHJEC7SM/wmnbB1Iiutxfo M629ulWtEukfv9gvv/zv1CHg9jMduF2hUmW/TU19XAoIAOFwKsE31r6K0BVRi+is 1ixoicC+p31L6UsxjQhLGDaMoY7482IMFqQ+Ieu7GkkIMZkIo9VM+YFQbg8nBSUN igeptUu3h0BAipx1kmwu7gJoki0XhlDqHwbjNcxBmcC+y5D7r1TQxN2b8nsxfUhP bvaHymB3vmQ6Bx+/sjh0f6wv3z2WrAG3Q0k4e7iZ4waVWPaSaFsszTHNMxaNp2iW fRDXsH6Kic87Js/w7OacBFbN00K1D4ZRucUFmJLM/A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdegledgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrf grthhtvghrnhepvdfffeevhfetveffgeeiteefhfdtvdffjeevhfeuteegleduheetvedu ieettddunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 May 2024 18:03:20 -0400 (EDT) Date: Wed, 15 May 2024 15:03:19 -0700 From: Andres Freund To: Alvaro Herrera Cc: Bharath Rupireddy , Jeff Davis , Masahiko Sawada , PostgreSQL-development , Dilip Kumar , Luc Vlaming , Justin Pryzby , Michael Paquier , Matthias van de Meent , Alexander Korotkov Subject: Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM Message-ID: <20240515220319.jzonzvw52wh4ltbl@awork3.anarazel.de> References: <202405150914.q2hc2cl2eqzf@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202405150914.q2hc2cl2eqzf@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2024-05-15 11:14:14 +0200, Alvaro Herrera wrote: > On 2024-May-15, Bharath Rupireddy wrote: > > > It looks like with the use of the new multi insert table access method > > (TAM) for COPY (v20-0005), pgbench regressed about 35% [1]. > > Where does this acronym "TAM" comes from for "table access method"? I > find it thoroughly horrible and wish we didn't use it. What's wrong > with using "table AM"? It's not that much longer, much clearer and > reuses our well-established acronym AM. Strongly agreed. I don't know why I dislike TAM so much though. Greetings, Andres Freund