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 1srcZ4-003IUC-3Z for pgsql-general@arkaria.postgresql.org; Fri, 20 Sep 2024 12:16:46 +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 1srcZ1-0054EJ-Tm for pgsql-general@arkaria.postgresql.org; Fri, 20 Sep 2024 12:16:45 +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 1srMVq-006RHn-2x for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 19:08:23 +0000 Received: from mail-qt1-x830.google.com ([2607:f8b0:4864:20::830]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1srMVn-0003ww-Tm for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 19:08:22 +0000 Received: by mail-qt1-x830.google.com with SMTP id d75a77b69052e-4582c62ee33so10071741cf.3 for ; Thu, 19 Sep 2024 12:08:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726772899; x=1727377699; darn=lists.postgresql.org; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=YqNG9lo/VvOArfx+H/sZLqQ5Dt8L4ZIOkHs7OO+XqyY=; b=mpdhPWCmKSuJwQVPiHIiz9c2FSuhevxF7SUlO12bji1SD6vN9pkbMd5hE6lfseRSSv Emyv7JvYhAgjFn2oZRfa5GPTQO9fHHgzjbgOF2utHBIk7vh4pm2StjWd9ZDS94ysYasL qllXP6+Ilr54xWg/HCfWzUHy2WEmLFCHH0aZb1wSFeR5rMVjipdk38p9GcXUiMnTEcbk wPktiBf9iy+N+qw5WvXpPVa5yjFggBktqdDB6fh9rt8m6yoP/ngEkDOhtJGfB5uM7yGR YiJIwjiE3n9ihWmESmSBJwrF+q1WiQsiHW+4Fmjrg8W1TeVlm1jUTzQlqm8vb22/sPKX jt0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726772899; x=1727377699; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=YqNG9lo/VvOArfx+H/sZLqQ5Dt8L4ZIOkHs7OO+XqyY=; b=TRH5H4tA9LiXB7g2/0aQrvjFaGpIe216zsNPeFmrXN0qZAPVlA1pWYnFZWIMy1bAtq BiRf+22PrN95/J4xb0gJyVQFYYQvvL9anHRJrdCoss4u1BExh5F+yM2yqDQtaHVUMz8J zx9G7Ag1y81VSTp7fOR/BppPfu71/rdhACQJAD10GcCW/T9QUy59BCAZS72enN2AxmX5 HZDIswT/cXzF69I9t4X/DpiygRizmSXSjrFePNdviY+kWs0fUhNqXxQEwJLUDGG/waSe 5d1eB6Njo+dbDvdCroxpRnekR+Edad08qc6TtDKf8UUGTjiKtFymxOFK4idfGUvQI2Cf 1yrA== X-Gm-Message-State: AOJu0YwyDuTUYx1WnOOZVs1Gu5dQYaXGTFw73yvmAipT9/M5bc9teiHk zhiXze1cYil4t9wy62KdDeXfC9nxWHmIHxUtg4kTMWxe9eceg6R20MIqgg== X-Google-Smtp-Source: AGHT+IEqYzF34H6cW9iGqg0wNDM9C5IW1Df2RVNNjZpUUSuRcIRIyRyUd7WqbFFzWxydYwzcIBIWGw== X-Received: by 2002:ac8:5fd3:0:b0:457:c74a:6386 with SMTP id d75a77b69052e-45b20511038mr7758761cf.34.1726772899272; Thu, 19 Sep 2024 12:08:19 -0700 (PDT) Received: from smtpclient.apple (syn-074-132-056-143.res.spectrum.com. [74.132.56.143]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-45b1788f8a5sm10028711cf.57.2024.09.19.12.08.18 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Sep 2024 12:08:18 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Wizard Brony Mime-Version: 1.0 (1.0) Date: Thu, 19 Sep 2024 15:08:07 -0400 Subject: pg_locks in production Message-Id: <230A1A3E-E09D-4A39-991A-DF739F4D12F8@gmail.com> To: pgsql-general@lists.postgresql.org X-Mailer: iPhone Mail (21E236) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk If performance is not an issue, is it valid to use the pg_locks system view i= n production code? Or are there other concerns besides performance that woul= d make its use inappropriate for production?