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 1t3K1n-00BsdD-R7 for pgsql-general@arkaria.postgresql.org; Tue, 22 Oct 2024 18:54:47 +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 1t3K1l-002DIc-Ph for pgsql-general@arkaria.postgresql.org; Tue, 22 Oct 2024 18:54:46 +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 1t3K1l-002DIT-Eb for pgsql-general@lists.postgresql.org; Tue, 22 Oct 2024 18:54:45 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t3K1j-002KVi-7l for pgsql-general@lists.postgresql.org; Tue, 22 Oct 2024 18:54:44 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-a99eb8b607aso647584366b.2 for ; Tue, 22 Oct 2024 11:54:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729623280; x=1730228080; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=5uynpknvpG7JCHuCvSOqPqSrVn16Qf/bBD28Mbtu1iI=; b=aWi2jzfYkKi0lXUkqqM8KZ2cNy1+G9zWIV05qo1BdJeaUBYzsQRixaKiicKx4FitUj I7L4tnSOerHZEQlKkVFHd8F9tTzC8BjPtQTfMvPiORi4MHamm4uTrR3a6BT2kS9ZWFms ehcoHU1tp5uuRmQAPY801lInboiQ5Nc0ez8CBEPyp6vO+jwboPTawSQM6a+d3MZT4lwn KKdU6vVVNGhlbcuoRCRTb/uaDBe6HyV3QynIWjtzK6HXX8a6FM0tvTVhy/aBjn+roKfW OVqbGxVb/7y/26x53LmKljz+0CXfmbYUPmW77wmCLmW0ef5eJ/QTVYEcusn6l2JfLPDy H7vQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729623280; x=1730228080; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5uynpknvpG7JCHuCvSOqPqSrVn16Qf/bBD28Mbtu1iI=; b=lkfA6G90YH+JMNl15NWB3IAGP8uQr6XxNMW8NP4AdbgBpmP3dqTFjzUIcW9Ck05HMn jaDOD0sCOChfOyma//OtuACnoi0bxqKTn1O7MRNyJtHARtljEVjOmkoDUeKuTFw1ZR8j XaOF3DB4ar/Ce10+etZIv1C5Q+DpSYnC+JX67afrngEAoCXR1cQinQNheTyfzs8lWV81 +ai+w4mItDsA32BwAjyHeey19BaRO+WudPk+2lBVIglGQT+C4b2IegMnZ+o9kvIphpfb NeltZQ+XhkTGp+yf3M/+06rnup6k46te2ndWns0YNh52gZQz6cEMKHkLJBMUIAqOOPUn xHyA== X-Gm-Message-State: AOJu0Yxed5V/3cjxrpdaCsyAZTz0TCcUrungNKoPuuDJuu71MLF+jRYC EGJDT7FbKifih6a4gUR8m5sC/txNBVclmT47ee93WD0xclUnDqr/ux5T1DjdOWI25hD6Wvas07U 3Q08JYRskFJibW1mGQv75ZJTzBKKzu6hR X-Google-Smtp-Source: AGHT+IHx17wZ+INhB6HcO4duOKX05p83lMjGhXqc4gMECWONZIfMO1hDMUGSFH4F4GM5Mi6JC1PcEUDcxNZM/sueEg0= X-Received: by 2002:a17:907:971c:b0:a9a:296:b501 with SMTP id a640c23a62f3a-a9abf8a221amr3405566b.26.1729623280303; Tue, 22 Oct 2024 11:54:40 -0700 (PDT) MIME-Version: 1.0 From: Durgamahesh Manne Date: Wed, 23 Oct 2024 00:28:06 +0530 Message-ID: Subject: Lock contention issues with repack To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000037c8bd0625154d0b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000037c8bd0625154d0b Content-Type: text/plain; charset="UTF-8" Hi DEBUG: Poll returned: 1 LOG: Command finished in worker 1: CREATE UNIQUE INDEX index_3199790649 ON repack.table_5832724 USING btree (id) DEBUG: ---- swap ---- DEBUG: query failed: ERROR: canceling statement due to statement timeout DETAIL: query was: LOCK TABLE offer.market IN ACCESS EXCLUSIVE MODE DEBUG: query failed: ERROR: canceling statement due to statement timeout DETAIL: query was: LOCK TABLE offer.market IN ACCESS EXCLUSIVE MODE While running pg_repack i was facing this issue as concurrent selects and updates on tables being repacked .However raised the same to pg_repack channel . No issues with low traffic on db How to resolve this issue even on moderate db workload ? --00000000000037c8bd0625154d0b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0

DEBUG: Poll returned: 1

LOG: Command finished in worker 1: CREATE UNIQUE INDEX index_31= 99790649 ON repack.table_5832724 USING btree (id)
DEBUG: ---- swap ----
DEBUG: q= uery failed: ERROR: canceling statement due to statement timeout
DETAIL: query was: LOCK TABLE offer.market IN AC= CESS EXCLUSIVE MODE
DEBUG: query failed:= ERROR: canceling statement due to statement timeout
DETAIL: query was: LOCK TABLE offer.market IN ACCESS EXCLUSIVE= MODE

Whi= le running pg_repack i was facing this issue as concurrent selects and upda= tes on tables being repacked .However raised the same to pg_repack=C2=A0cha= nnel . No issues with low traffic on db=C2=A0
How to resolve=C2=A0this issue even on moderate=C2=A0db workload ?



<= /div> --00000000000037c8bd0625154d0b--