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.96) (envelope-from ) id 1wAa9H-0006hy-0v for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Apr 2026 21:09:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wAa9E-0029Cj-2R for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Apr 2026 21:09:17 +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.96) (envelope-from ) id 1wAa9D-0029Cb-2X for pgsql-hackers@lists.postgresql.org; Wed, 08 Apr 2026 21:09:17 +0000 Received: from fout-a1-smtp.messagingengine.com ([103.168.172.144]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wAa9B-000000003TE-2Nhj for pgsql-hackers@postgresql.org; Wed, 08 Apr 2026 21:09:15 +0000 Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id 1A591EC0410 for ; Wed, 8 Apr 2026 17:09:13 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-02.internal (MEProxy); Wed, 08 Apr 2026 17:09:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm2; t=1775682553; x=1775768953; bh=mAjRxV7ZAo55sxlAu4+96CuP7O7+Ya02 h5RRZ1rIGvQ=; b=eB2yuAz8hAf4i8SjxMk2iF2R3ZY1oyG+GxXyEYAF94s2LZnW qnmRidvToispERWauz5Ea0DSttU3/92Rw1ljUt3PZHyendreJQvCELstOJc44KKY baU1mSH6yLUpwQsF+P7Y7wglzT6pq06NOu2Vlmpo9o7U61ku08g8n5l9qccqmTQr Bjhm7t7K9Wq8Z74lz+VWWEtviGQ0htscuqIUrFPUV+cWQ5mnuvK4xXsPOMGCh4pu QeaAY4bTJJHRolFwD/NgZtbsF/TqTSo51N6gpvTT5eEPIs5Vk3FxIROKYvfadI2u /8N1gL1Hd81D8IlM5YLANN683/TMl5PhTFHPYA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1775682553; x= 1775768953; bh=mAjRxV7ZAo55sxlAu4+96CuP7O7+Ya02h5RRZ1rIGvQ=; b=n MTzrjP0uhtPLGhHqeTvXt3syIZZZ0DIVB4M6Qx/NBxu7zw5TiJpHUDeczRrYBFeC 8dY5MeVHlqR4D9CzkCnZWHj4+9J4n9rucQODkGuC01G1KXA/Pysuprn1lI1oniyz pAP164yeGFIUa7d7b/l5aZyADdrHMSEfOyJ7PQ+QQq0s4Wh1+Ii98bJRqltLsjdq 1p2enZW+/ZLoS8KQ38frJ4IvqiauK7TsOT/ncxi3mGb+TdVP6cnjdMvY4DmA3Ooe dMd1gPNdQuDgThlYROF04aI0sWs07NxCqz70T0Bh+zI/gjdKs1xNl8Fl0uB0HYai 2AN46DzIN5sRSWOPip0Ag== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgddvgeeiudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehmtdfsredttddvne cuhfhrohhmpeetnhgurhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigv lhdruggvqeenucggtffrrghtthgvrhhnpeegffejuddtvdfhhedvffegjeeiueevkedthf dvgfevieevheejueejffdvuddtkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgiivghlrdguvgdpnhgspghrtg hpthhtohepuddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepphhgshhqlhdqhhgr tghkvghrshesphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 8 Apr 2026 17:09:12 -0400 (EDT) Date: Wed, 8 Apr 2026 17:09:12 -0400 From: Andres Freund To: pgsql-hackers@postgresql.org Subject: s/pg_attribute_always_inline/pg_always_inline/? Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="nrl6kihukes5f4e7" Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --nrl6kihukes5f4e7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, When reviewing the index prefetching patch I got a bit dismayed at how long pg_attribute_always_inline is due to the way it triggers pgindent to format stuff. I propose that we remove the _attribute_ part of the name. Given that it is implemented for compilers that don't use the __attribute__((always_inline)) spelling, so the shorter name seems better anyway. Thoughts? Greetings, Andres Freund --nrl6kihukes5f4e7 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v1-0001-Shorten-pg_attribute_always_inline-to-pg_always_i.patch"