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 1vtjWG-008YHw-0o for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Feb 2026 09:43:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vtjVF-009cpx-1J for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Feb 2026 09:42:21 +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 1vtjVE-009cpp-2p for pgsql-hackers@lists.postgresql.org; Sat, 21 Feb 2026 09:42:20 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1vtjVB-00000000UmP-1qGE for pgsql-hackers@postgresql.org; Sat, 21 Feb 2026 09:42:19 +0000 Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-48371119eacso28809965e9.2 for ; Sat, 21 Feb 2026 01:42:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1771666936; x=1772271736; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=aiFJngHFV6ud7Oo6mb01bUQpxHBuBFmLVOmb6RmHxDU=; b=ctY/FZ9Jj90sd+FHTJAqi2OnOyH4mBpBtl6F9yWdK2AGF4gNR0+gmcejxNM4yA6LGb +yc9fvCgXsinvPxcrRehWwH4dYxtj05P/HxMTT5oFetb8YaQHUztym62RGafaq1+dvq5 Tdq44nQi81a6B3IkEvnHVSv0GrrlkGHtnTYu6cF/KRgoRQMRgH1PMimSv7+o5/GUmrOd +p1X4Z7Km8APEaw+NyXb2gWIcMF0oq+bxhZsgsqia/c1s8IqXF6+XxtrcTf06bfJyLsd tPSIZ2XkOOypTxR35UWjRXBE8FrfOEW+4BXQ9xuto/8l8HbV62+H/pa6XeX1zd8EpSC4 FTng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771666936; x=1772271736; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=aiFJngHFV6ud7Oo6mb01bUQpxHBuBFmLVOmb6RmHxDU=; b=Lnz6xsnvAC/6nngKBufLEsJ9MiC/Jnin/E9swuAQxvdFa48q6bxWyYQ4NFA7K8uYrx QdxOraGRRzaBItB4DnfsavLpRIuWbOQs3tZbAipUcrGSSWF70oxPQGAbfenO7zRt9Oa4 WdLWzNhq8m0Nm3vOIj5DpqnFhwIPT9s4F/84iBjsbUBCfAAjT6c8ndRwaQURcvP9f9rE aoX/K3EAx6nLjbzvWlimEh9eWMznALHtI/aXoESUu/TRSwnYoJ1L4VcgDehwkiUakBqX DUYRiA09kLpg+6eWx2CtTIkpcOdSOoPaKIjqGKF8XJms0083UTjmTsXXfSHpuayQ40O7 FYFw== X-Forwarded-Encrypted: i=1; AJvYcCXv1UQLDyYzLudYQiIy6expLU1GWYuvtF/SVFdzx7RolUVxxE6zpA2PYPdE807YMFnYPXZ9bVhu97WFeNZe@postgresql.org X-Gm-Message-State: AOJu0YymlhHKxgEmcT54YVFMpajJswsnKjR4tQ79rUTB94BugnUyZ8jN ZQLOtfAjdmFV+Gp61sV3u2jT5P3/NWF8La6GfIwmLkmKFyp729TpKvdZ X-Gm-Gg: AZuq6aKKpuBDA1S4m8yJQgkfkG/Upgot605kRrWS+MXbAfKnwpvhN+K8kFJlpu0TCZx uWZ4GEKO+jfj8E2uWcYPtxxLGOL7DnM/GDcdiImthCrHitBYL4S+Xdsu3U15iWHGM3lFSSTdCcv LoAIIrGt6mBKm63yA8MjHpOdqzbu/u2Fpsj4Hot/ompAKpkr4gjk0nv1MrM5mBPSCvJQGvGlClC tw9mQ5Kq2YjR7w6AsOgBs5v03DSRCLv8oN2yHsM9ierJKl+CPPyt3/ROrT+YO4pTX+JEnLqerh/ vquCU2cuazVZvQFC0nKKnja/uFK90iYCYeoM8nuiKYsI0g6lypvphDd4WfNnXyYL/AycbYgZOwO 4NONj1VBvCWWQEt1OsTkJ7g5b5OV+bNh1jNRvnvXA7OJlG7lSWR29jamFMLaEN4ZjuenNU/GEHh EO/FGuxeZAJ5AVzCS3uKKB895su2rm69rjozXNuL1uAPndn6XHJ/uuslZxqKQi4zE5uphhUOlbr oofh+G4YHQvKZLAf+XW4XXPY0kLB2XnB8nxq+nWzXolcMgvacXgLkYz+km8VIZ3fxdX X-Received: by 2002:a05:600c:3553:b0:47e:e87b:af8 with SMTP id 5b1f17b1804b1-483a962e491mr39463455e9.21.1771666935777; Sat, 21 Feb 2026 01:42:15 -0800 (PST) Received: from ip-10-97-1-34.eu-west-3.compute.internal (ec2-15-237-197-144.eu-west-3.compute.amazonaws.com. [15.237.197.144]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-483a42f7d8esm34800835e9.25.2026.02.21.01.42.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 21 Feb 2026 01:42:15 -0800 (PST) Date: Sat, 21 Feb 2026 09:42:13 +0000 From: Bertrand Drouvot To: Heikki Linnakangas Cc: Andres Freund , "pgsql-hackers@postgresql.org" Subject: Re: PGPROC alignment (was Re: pgsql: Separate RecoveryConflictReasons from procsignals) Message-ID: References: <1cb0d7e9-d6dd-4517-a7cd-0ad98e1207f3@iki.fi> <3dd6f70c-b94d-4428-8e75-74a7136396be@iki.fi> <787be980-0878-4f4a-be01-d042ab5d370e@iki.fi> <60478a2d-915e-411d-9f7d-42917dd8b8c4@iki.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60478a2d-915e-411d-9f7d-42917dd8b8c4@iki.fi> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Fri, Feb 20, 2026 at 11:03:09PM +0200, Heikki Linnakangas wrote: > On 11/02/2026 06:40, Bertrand Drouvot wrote: > > That looks ok to see PGPROC as an "acceptable" one, if not, should we use the > > union trick? > > It seems acceptable to just not align it if the compiler doesn't support it. > This is just a performance optimization, after all. Agreed. > Attached is new versions the remaining patches. I think these are ready to > be committed. Thanks! One nit, 0001 is adding the typedef: " -struct PGPROC +typedef struct PGPROC . . . -}; - -/* NOTE: "typedef struct PGPROC PGPROC" appears in storage/lock.h. */ + uint32 wait_event_info; /* proc's wait information */ +} PGPROC; " Would that make more sense to add the typedef when we introduce the explicit alignment in 0002 (like it was done in your previous v2-0001-Align-PGPROC-to-cache-line-boundary.patch up-thread)? Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com