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 1qo74A-000Ccz-21 for pgsql-admin@arkaria.postgresql.org; Wed, 04 Oct 2023 18:57:50 +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 1qo739-002fQp-BE for pgsql-admin@arkaria.postgresql.org; Wed, 04 Oct 2023 18:56:48 +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 1qo738-002fQe-UK for pgsql-admin@lists.postgresql.org; Wed, 04 Oct 2023 18:56:47 +0000 Received: from mail-yw1-x1131.google.com ([2607:f8b0:4864:20::1131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qo737-0002fi-Bs for pgsql-admin@lists.postgresql.org; Wed, 04 Oct 2023 18:56:47 +0000 Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-59f6767a15dso11810477b3.0 for ; Wed, 04 Oct 2023 11:56:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696445803; x=1697050603; darn=lists.postgresql.org; h=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=mZKUJEk/UV/thN/sPfrK6opPOSfCkeAs85cgBtqNg6E=; b=CCRmhHmxZh+vPMICGQgVIi3hQJfaI0sR0EXd1QbX2xb/YzlZOv0k5GiJyfxKB9CZWs EO13Pm/n5ai5ggk7T/4mEJGIwqaoaqhlcNoQKml1SqFMJEdhkyazD5iO/6VahyMyc+z1 IQMfYQ0HrjeEmA7gPzeTSFzKSIsDv+6r9uKUoWb6uzWbaXNxAwhvDTNIpMJ9me3Vg+Qw +SgYzwjqBxvuH6TkOLGEMKE82ZFgrL0OvYF4Q2WQuUKsD/PdBJmDqrOH2sONHlJJC4/x FsPxIejRwLk/yFA/NaR7x2/nS7yFjf3AVMIM3S+/wvjhtHV+k/9lqOs1lNEnhUqgOfP8 OXaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696445803; x=1697050603; h=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=mZKUJEk/UV/thN/sPfrK6opPOSfCkeAs85cgBtqNg6E=; b=vUykliHvIOdk4ICHxhSzh7QOSWbZ6hSy6AWzjqjAswVoZzYOQ7QQzdZC3JP58Djf3q GTLtxSNFRNel+nMVAdoHeUmm1t4tk5fc4jvsK9OqmIBf8GZ6/KwE/bwIcfHBZcGDNt+g x4JU56e/D/pv9CfN8C7KbKbgOV/HeocX8LO4B0X8UEfDSvaDyakTNFpXVb/6z5ynz7sd DstHMxnan81t85cpwIKWo5ONZzRPDXlsI9Mzv+1Kepi+qDJGORZsF4LcotyZIWn+dKNU 8Fu7sh9r3eq8jddbnpTY12Ipw1eUuc2JQspCumYbm+VZtsXvlMhFvtrksGMer7ljL4qI jIfg== X-Gm-Message-State: AOJu0YzwLWZ42M3VMQ0Cs1F3xHaSuSLdN1GnyebZRndCDWDgRmlPnS9a 0jfoX46Ed/aDw2W+w9KgjEUCTTh8DPM= X-Google-Smtp-Source: AGHT+IHpTBeNBB+kjvQUXJUTgIH+PqGR8W1oG8DmyZ+IqRgkj5w92ycOZD0TiBaVYk+6o4n/PQjMmA== X-Received: by 2002:a25:a423:0:b0:d4a:499d:a881 with SMTP id f32-20020a25a423000000b00d4a499da881mr501334ybi.9.1696445802748; Wed, 04 Oct 2023 11:56:42 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:e883:e8ce:417:6969? ([2600:1700:bd2c:b810:e883:e8ce:417:6969]) by smtp.googlemail.com with ESMTPSA id 82-20020a251655000000b00c64533e4e20sm1225411ybw.33.2023.10.04.11.56.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Oct 2023 11:56:42 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------jEjBX0O7N4aExCB25ER44RoM" Message-ID: <86c77066-b696-9c0f-a4e9-8f9bc5b48048@gmail.com> Date: Wed, 4 Oct 2023 13:56:40 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Timeout Issue Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------jEjBX0O7N4aExCB25ER44RoM Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/4/23 13:13, SOzcn wrote: > Hello, I am getting an error like the one below in a cluster. > > ==SQL Error [57014]: ERROR: canceling statement due to statement timeout > > The system generally works normally, but whenever I try to create or drop > an index, I get this error. > > Frankly, I tried many methods to fix the error. > > Like changing the index name and trying to instantly delete it. > I stopped all applications connected to the database and tried again. But > the result was the same. > I did not understand how I got this error even though there was no session. > > I also examined the Postgresql Logs, but there was nothing enough. When I > started this progress there is no any load on my database server. > > I using Postgresql v13.9 > > *2023-10-04 18:32:56.669 +03 [1339952] [user=user,db=dbname=DBeaver 21.2.1 > - SQLEditor ] ERROR: canceling statement due to statement timeout* > > *2023-10-04 18:32:56.669 +03 [1339952] [user=user,db=dbname,app=DBeaver > 21.2.1 - SQLEditor ] STATEMENT: drop index dbname."indexname" > > Any advice?* > Look at what the statement_timeout value is set to.  For example: postgres=# SHOW STATEMENT_TIMEOUT;  statement_timeout -------------------  0 (1 row) -- Born in Arizona, moved to Babylonia. --------------jEjBX0O7N4aExCB25ER44RoM Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 10/4/23 13:13, SOzcn wrote:
Hello, I am getting an error like the one below in a cluster. 

==SQL Error [57014]: ERROR: canceling statement due to statement timeout

The system generally works normally, but whenever I try to create or drop an index, I get this error.

Frankly, I tried many methods to fix the error. 

Like changing the index name and trying to instantly delete it. 
I stopped all applications connected to the database and tried again. But the result was the same. 
I did not understand how I got this error even though there was no session.

I also examined the Postgresql Logs, but there was nothing enough. When I started this progress there is no any load on my database server.

I using Postgresql v13.9 

2023-10-04 18:32:56.669 +03 [1339952] [user=user,db=dbname=DBeaver 21.2.1 - SQLEditor <Console>] ERROR:  canceling statement due to statement timeout

2023-10-04 18:32:56.669 +03 [1339952] [user=user,db=dbname,app=DBeaver 21.2.1 - SQLEditor <Console>] STATEMENT:  drop index dbname."indexname"

Any advice?


Look at what the statement_timeout value is set to.  For example:
postgres=# SHOW STATEMENT_TIMEOUT;
 statement_timeout
-------------------
 0
(1 row)


--
Born in Arizona, moved to Babylonia.
--------------jEjBX0O7N4aExCB25ER44RoM--