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 1saxEx-00CVZ3-EO for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Aug 2024 12:55:07 +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 1saxEv-00DerG-Jd for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Aug 2024 12:55:05 +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 1saxEu-00Der8-Cp for pgsql-hackers@lists.postgresql.org; Mon, 05 Aug 2024 12:55:05 +0000 Received: from fhigh7-smtp.messagingengine.com ([103.168.172.158]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1saxEr-003DaI-41 for pgsql-hackers@postgresql.org; Mon, 05 Aug 2024 12:55:03 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 337561151B7F; Mon, 5 Aug 2024 08:55:00 -0400 (EDT) Received: from wimap21 ([10.202.2.81]) by compute7.internal (MEProxy); Mon, 05 Aug 2024 08:55:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=compiler.org; h= cc:content-transfer-encoding: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=1722862500; x=1722948900; bh=OEw6KsgMUoJK087AUH+wLMPI4Yr10w3v8xZNSgK1Ecw=; b= QpGw72jsEc9jdeWiXUR2z+nWl+H26BvSeZU9Lclw0K1cNG4NJmDmNw+qehfzNSLj g/iYaMpiF3Ck5k2vUYDAuY6Vqt0engkC12155JwGDJqbekkhHS+qouj07XFQ65yH GGclr1h86AbOrWyfENlWgPIy43s/7YpbdtMFtkrJ/GiQ4SIrm6NNFn2mQcbOwuYR wo0IeTAg1slaq+vUKbgS+Gf7tIxhY6kxk1uBPcTBKRCccSjVTdHO6MX9LkXVZlJR cm0jmeFJaTCPx0BSpWAuD3ILTn+xMuA+LK7L1Ygc3sNYBqGiapasAyIJnrJIfIXz KTopSE+eENwcoRf1iaVpYg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=1722862500; x= 1722948900; bh=OEw6KsgMUoJK087AUH+wLMPI4Yr10w3v8xZNSgK1Ecw=; b=G +TcbaBnnsxJCMwqrgpzVZxqo+pDZCIjbkbOBNiMSenJ0M8PYSZWDKfm1i2VZ8d6N x6q0zb3FADRxjcHwM9MheRfS7erYVh/jyB6+XO4WMy34a7CsTQQLJRdKG0RwJocD 0NvYDWe237u3mg0rBSuSws61ku/hWvQeR57ditZ29FE/xrU8E/a1Hp/KkXXapnuq JEVR1/nL4kF8XHbNVn0X0oodP4lp20lZnnazSfG0bLh+r388nhbXESSzOqyV6lfp MM8c5tIonZLBM3jY9ENeoFnTd4/LsS3A0m56bW+Hh9oQ4ivgJn0Chmo9gvtMLZY0 HQEW92XYZ8R2xL+KgL/kA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrkeeigdehlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefoggffhffvkfgjfhfutgfgsehtjeertdertddtnecuhfhrohhmpedflfhovghl ucflrggtohgsshhonhdfuceojhhovghlsegtohhmphhilhgvrhdrohhrgheqnecuggftrf grthhtvghrnhepveelffdtiedugfdvgffftddvieevleetieetgfettdffjedtjeefffel hfelffeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epjhhovghlsegtohhmphhilhgvrhdrohhrghdpnhgspghrtghpthhtoheptd X-ME-Proxy: Feedback-ID: ic6394509:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 05BF937A0085; Mon, 5 Aug 2024 08:55:00 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface MIME-Version: 1.0 Date: Mon, 05 Aug 2024 14:54:39 +0200 From: "Joel Jacobson" To: "Aleksander Alekseev" , pgsql-hackers Message-Id: In-Reply-To: References: <73b34bf6-d2d8-4eb9-acb6-5a8cdf11674b@app.fastmail.com> <5859e123-2fb1-4160-8999-bc8bcf51fba0@app.fastmail.com> Subject: Re: Is *fast* 32-bit support still important? Content-Type: text/plain Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Aug 5, 2024, at 14:24, Aleksander Alekseev wrote: >> Could we add a text message that is displayed to a user, >> when compiling PostgreSQL on a 32-bit platform? > > What would be actionable items depending on the results? Option A: > someone claims to use PostgreSQL on 32-bit hardware. Option B: no one > admits that they use PostgreSQL on 32-bit hardware (but maybe someone > actually does and/or will in the future). Regardless of the results > you can't drop the support of 32-bit software (until it gets as > difficult and pointless as with AIX that was dropped recently) and it > will not tell you how slow the 32-bit version of PostgreSQL can be. > > If there are no actionable items why create a poll? Never suggested *dropping* 32-bit support; that's a different question. However, if we were to receive input from 32-bit PostgreSQL users explaining why they need *high performance*, then I imagine that could affect how we feel about 32-bit optimizations. Right now, there doesn't seem to be a consensus on whether we should optimize for 32-bit or not. On the one hand, we have commit 5e1f3b9 that says: "While it adds some space on 32-bit machines, we aren't optimizing for that case anymore." On the other hand, we have the ongoing work on optimizing numeric_mul, where a patch is suggested with extra code to optimize for 32-bit. I agree, however, that the absence of any comments from such a poll would not give us any more information. /Joel