Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1mmdrY-00040D-7R
	for pgsql-performance@arkaria.postgresql.org; Mon, 15 Nov 2021 15:25:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1mmdrX-0006Z4-6x
	for pgsql-performance@arkaria.postgresql.org; Mon, 15 Nov 2021 15:25:39 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1mmdrW-0006Yv-Tb
	for pgsql-performance@lists.postgresql.org; Mon, 15 Nov 2021 15:25:38 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1mmdrU-0003NN-Ih
	for pgsql-performance@lists.postgresql.org; Mon, 15 Nov 2021 15:25:37 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 1AFFPVaE2123131;
	Mon, 15 Nov 2021 10:25:31 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ashkil Dighin <ashkildighin76@gmail.com>
cc: Andres Freund <andres@anarazel.de>,
        "pgsql-performance@lists.postgresql.org"
 <pgsql-performance@lists.postgresql.org>
Subject: Re: Lock contention high
In-reply-to: 
 <CAH6zzqBhFXVNKT7T=CbZ65fQS++h6vG3fhewWytWvxPskQHWKA@mail.gmail.com>
References: 
 <CAH6zzqCNtbCDSSFweuZp93R7TOxfEB8f75iosExb6sutyAa-Uw@mail.gmail.com>
 <20211025233546.byihrwehpi4feqv2@alap3.anarazel.de>
 <CAH6zzqDrwOoTMnh=rPBwcK-DA4wuEQGNtZdtLXY+7fXmDXHW9w@mail.gmail.com>
 <2A5AB443-64E5-42DC-936A-C521ADD6B1BD@anarazel.de>
 <CAH6zzqBhFXVNKT7T=CbZ65fQS++h6vG3fhewWytWvxPskQHWKA@mail.gmail.com>
Comments: In-reply-to Ashkil Dighin <ashkildighin76@gmail.com>
	message dated "Fri, 12 Nov 2021 19:42:30 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2123129.1636989931.1@sss.pgh.pa.us>
Date: Mon, 15 Nov 2021 10:25:31 -0500
Message-ID: <2123130.1636989931@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/2123130.1636989931%40sss.pgh.pa.us>
Precedence: bulk

Ashkil Dighin <ashkildighin76@gmail.com> writes:
> I suspect lock contention and performance issues with __int128. And I would
> like to check the performance by forcibly disabling int128(Maxalign16bytes)
> and enable like long long(maxlign 8bytes).
>  Is it possible to disable int128 in PostgreSQL?

Sure, you can build without it --- easiest way would be to modify
pg_config.h after the configure step.  But the idea that it has
something to do with lock contention seems like nonsense.

			regards, tom lane