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 1qh5T1-00190j-Qb for pgsql-performance@arkaria.postgresql.org; Fri, 15 Sep 2023 09:50:28 +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 1qh5T0-00FncH-Ff for pgsql-performance@arkaria.postgresql.org; Fri, 15 Sep 2023 09:50:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qh5RY-00Fi7j-KE for pgsql-performance@lists.postgresql.org; Fri, 15 Sep 2023 09:48:56 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qh5RU-005DC6-Vb for pgsql-performance@lists.postgresql.org; Fri, 15 Sep 2023 09:48:55 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A8FFB5C00F2; Fri, 15 Sep 2023 05:48:50 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 15 Sep 2023 05:48:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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 :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1694771330; x= 1694857730; bh=FFPm5PMSPWbVHa+NzeSqjgnqP8DfNPQ1DJBG1oC7U74=; b=e MP2ZAw+y7D0w3ZCLmSO5wb0K5ulMgJIDkaUxhpCtA9aupUiP6R2yDcSfieJ15keV f69Ego2c0wDCBNx7GyzplccGicp3JF2HM4/oRL1sfu+gNqBvHncr9daaDwkRwouM +SWPU29EZs/360zWBGwVfu2bUEhm/lYMs0nFAZ/D+57HNmdH94rgNwhIT9/W94/N sGiz4t7VLdXBDI7FGGZ33Gsow//K+moT+xEmEUbAZJQOJwXV8HFnAK+qnG+ncDUL GXPNFGsPGWe8beBAv+DUjBBCdWYgaM+vHgYFZEU8hveu7KHCwv/Dyqgy3NZggJ1c ZBjzCDcsRnngZz9N7Ifng== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudejvddgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfggtggugfgjsehtke ertddttdejnecuhfhrohhmpeetlhhvrghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhr vgesrghlvhhhrdhnohdqihhprdhorhhgqeenucggtffrrghtthgvrhhnpedvkedtffduff dtffffheffhfejjefhgfeiueeukeejkeffgfdufffhudffffeuveenucffohhmrghinhep vghnthgvrhhprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhr gh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 15 Sep 2023 05:48:50 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 13AFAA7; Fri, 15 Sep 2023 11:48:47 +0200 (CEST) Date: Fri, 15 Sep 2023 11:48:47 +0200 From: Alvaro Herrera To: bruno da silva Cc: pgsql-performance@lists.postgresql.org Subject: Re: Multixact wraparound monitoring Message-ID: <202309150948.c7fwqegp2f4i@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Sep-14, bruno da silva wrote: > This problem is more acute when the FK Table stores a small number of rows > like types or codes. Right, because the likelihood of multiple transactions creating new references to the same row is higher. > I think in those cases an enum type should be used instead of a column with > a FK. Right, that alleviates the issue, but IMO it's a workaround whose need is caused by a deficiency in our implementation. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Pido que me den el Nobel por razones humanitarias" (Nicanor Parra)