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 1whykh-000WEM-0G for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Jul 2026 00:05:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1whykd-00FEFs-0g for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Jul 2026 00:05:55 +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 1whykc-00FEFk-1v for pgsql-hackers@lists.postgresql.org; Fri, 10 Jul 2026 00:05:55 +0000 Received: from relay4-d.mail.gandi.net ([2001:4b98:dc4:8::224]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1whyka-00000000OVT-1MSL for pgsql-hackers@postgresql.org; Fri, 10 Jul 2026 00:05:54 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 77FB03E802; Fri, 10 Jul 2026 00:05:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1783641944; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2mmlv4qO5C/mJi4h+cS2eGrHKEeF0usMUF51vseC/Ms=; b=Swe2ctHxMABhwgyJnGePzyAhfSJQkHgYE43Lx9xt0OXSyvsaMe7RWkVYodtUBZM04mg2XP 9IUWi4ubn+t5Rg3sOAyT1bqjiVBdy5zK6bA+P9wmNuXUj4EMGPL43W4tVH/bpLXhV3lXNi Uli7gKUgn/1/r8Kc0HGG4BtKix4B5nsNd2XPHLq96K++9cBxNJeVbyVH0cnUbNoc2DOEY5 h9g8hajhj8nzqz9Wa5TPFcVcTOCfVq67rT807Cy5PY4joesNEkVCEjuMRf0MqSLwVkX7zj sxbNtpMo6Qoc7kJofKMWdvNSNBKH1mGmnQPDdqIvK8z0hPCdQsMpzwe/o6fiKQ== Message-ID: <3184af6f-75a2-4b43-8223-897b71970fef@vondra.me> Date: Fri, 10 Jul 2026 02:05:43 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: s/pg_attribute_always_inline/pg_always_inline/? To: Tom Lane , David Rowley Cc: Peter Geoghegan , Andres Freund , Peter Eisentraut , pgsql-hackers@postgresql.org References: <56def459-2b95-42bc-b4e4-26e57f08b064@eisentraut.org> <4370bec0-df13-40f3-92ee-75974182e41f@vondra.me> <2391698.1783556089@sss.pgh.pa.us> Content-Language: en-US From: Tomas Vondra In-Reply-To: <2391698.1783556089@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-Sasl: tomas@vondra.me X-GND-State: clean X-GND-Score: -100 X-GND-Cause: dmFkZTG1o/eqTwzFZ04xwaXvrA3PQB+8dTarHMMcmUBcYxpNGG9+nbSQ687G/Iv1NiPy35HuK6zG+hkxKn6qFpkuf2XJJc+rLy0BgGwQANAaY68zFouT+S4B2iK9lU87ZyZzt0lSgDkUeEj9pJQDckA8h9LofCXBOvIKKJ9uf51/yawaVvlkW7MZfouFv8ZjidpCHssRhfukJ4NsPUJc8aRAaHLzFMIbbIuXCPcpZzk3vgcY5rll0D0rKyupoaiMzUWmSgD9MpdiTrxeQus77IC/hUMPoJVTPcCooXmBqyvzE+e7dcMKnQkB4sW9kv9OfZvmE+cV3wOvQrpuHUlkC2CioLXMGmTM0tjjwmNE50emOQcQ6Kgyk4aF8CzKuTh3JXWJPvcrVfT30gaCxtw9W8PvKGftLNgiiuTZnNrcfxHJ0UIa/tp8aYYkxpSNHuCU5xc2yQaWgpl+ZE3qcroqRnAsn2OVd31Q2qHeQooIRDFmDGNRdrrTANNCxC4OgEL+Vi5R3C66DXLk8IcavP3f+BUrhlelQTW285OqCDwSepxZT3IZy3uUopvKS/xy5gtoi0G934yjl+sEIOIO1HQOxgactzBFL5hFFON560eHH4Ppc5hdtiqqP73xHPiyj0JGo6y7yOsxG/VdSFRTPs3v8yqweQ3bR//VGSH6gShYTmeo8FFkZA List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/9/26 02:14, Tom Lane wrote: > David Rowley writes: >> On Thu, 9 Jul 2026 at 09:42, Tomas Vondra wrote: >>> I guess we should just commit that, so unless someone objects soon I'll >>> just do that. ISTM the agreement is to backpatch this too. > >> How about just backpatching the new macro and leaving the old one in >> place back branches? > > +1. Breaking valid code in released branches is unfriendly. > OK, that sounds reasonable. So in the backbranches we'd have both pg_always_inline and the original pg_attriute_always_inline. Does "backpatching the new macro" mean we'd also adjust all existing places to use the new macro or not? I mean, we could backpatch just the bit in c.h. I plan to adjust the places, to minimize possible conflicts when backpatching other stuff. regards -- Tomas Vondra