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 ) id 1oypgg-0007bl-Jy for pgsql-general@arkaria.postgresql.org; Sat, 26 Nov 2022 07:33:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oypge-0004KS-3q for pgsql-general@arkaria.postgresql.org; Sat, 26 Nov 2022 07:33:20 +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 ) id 1oypgd-0004KI-NT for pgsql-general@lists.postgresql.org; Sat, 26 Nov 2022 07:33:19 +0000 Received: from mail-qk1-x733.google.com ([2607:f8b0:4864:20::733]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oypgb-0005MS-Ou for pgsql-general@lists.postgresql.org; Sat, 26 Nov 2022 07:33:18 +0000 Received: by mail-qk1-x733.google.com with SMTP id i9so3954993qkl.5 for ; Fri, 25 Nov 2022 23:33:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=fbqPS3GyH4sP0VnX6vB/uqQmrV8sYDboErLCyDvXVXQ=; b=e+I3z17AjgUuyopK1M2gotnxkNxhZwVX9xeY+x2lMDyS2OF8qbeMTgxe2U8aIkjJ0Q VUHia3rGhReEy6lAv9G3CBzfSbt5DQV5hjyNGnCITqG7rAzeCztsY2bRCEJvAMNaoGug S+yoZDpsv9bYF3so1EeR0GTuliKyfvJSyppvs6uUhC1KstSB/zcOYuEsm9GevsV52nBr PZUZJe07LMkS7cPQScMdl3T5mJjoVaXVbB8pR3I6TbcyiIp+FWuMCfn8/kcfDbOjxdPV poNKZTOJjg9csqG0tgaMy7rDTSgt6lI2lcuNa1wSXvDQjfbP1dEuBJwRn47ushK4dzuE Nbiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fbqPS3GyH4sP0VnX6vB/uqQmrV8sYDboErLCyDvXVXQ=; b=TGRRnMOaevqujTWiFkTkXoqVhp3KyoQmtkRyjBDGmRU+zDjvYqYP3DBL/mvyldtXZF bVVX1NuvoGBPilCnDolWq7Xy8OmuYf/f2LzN04s6A7Q+zQkJo+4kNnZNU9rQOQlRj/Y9 Y6b0JI3DVQxYM2qtw6McSow8ijfletSLZqKe/ISbiD58CJ6HAMhQOnnzjM2Z+/prGvZC T3lNvt5wrLyJkJf1GV4flDa3uANwE8mGgN9vOvTFrvYANLSC/SUpxFXq+dABCat7+Smc M9zZOREDrEAfNdoqzqIlYZCCjwePU8aLrIOkq4PT1Vrp52Rf21ciOEkpxvdCmTrNfyOh l9Mw== X-Gm-Message-State: ANoB5pncUpGw9fJ9ijJAxNQ2L6zjLjBBKGqviStNBCeGYThbbHo8g2YN 8ExNmaohJDF/qPubaTImSbHTfRUX6/0= X-Google-Smtp-Source: AA0mqf4wJpyL/BxeWQ4laon03cVXFDPkjNoNAd/uBV2OnphyBHTCrd8ik2ObFkWlJGL11j4u1ZqKiA== X-Received: by 2002:a05:620a:6d7:b0:6fa:a605:ea6c with SMTP id 23-20020a05620a06d700b006faa605ea6cmr37139229qky.465.1669447996580; Fri, 25 Nov 2022 23:33:16 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id do39-20020a05620a2b2700b006cdd0939ffbsm4113053qkb.86.2022.11.25.23.33.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Nov 2022 23:33:16 -0800 (PST) Message-ID: Date: Sat, 26 Nov 2022 01:33:15 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: Practical maximum max_locks_per_transaction? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <25925.1669420577@sss.pgh.pa.us> From: Ron In-Reply-To: <25925.1669420577@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/25/22 17:56, Tom Lane wrote: > Ron writes: >> How "raised" is too raised?  I just had to increase >> max_locks_per_transaction from 640 to 1024 on an instance with many child >> tables and against which is run many large reports.  Another instance has >> zero children, but had to increase the value to 1280 to prevent reports from >> failing. > max_locks_per_transaction in isolation means nothing. What counts > is the product max_locks_per_transaction * max_connections, which is > (more or less) the number of slots allocated in the shared lock table. > > Having said that, you can probably make it as big as you want > on any reasonably modern machine. I wouldn't blink at a few > million locktable entries, at least not on 64-bit hardware. Really good to know.  I wonder how that can be worded in the documentation. -- Angular momentum makes the world go 'round.