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 1qo79y-000D00-OR for pgsql-admin@arkaria.postgresql.org; Wed, 04 Oct 2023 19:03:51 +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 1qo79w-002n2P-CO for pgsql-admin@arkaria.postgresql.org; Wed, 04 Oct 2023 19:03:49 +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 1qo79v-002n25-W7 for pgsql-admin@lists.postgresql.org; Wed, 04 Oct 2023 19:03:48 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qo79u-0002iV-7G for pgsql-admin@lists.postgresql.org; Wed, 04 Oct 2023 19:03:48 +0000 Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-405361bb9f7so1196715e9.2 for ; Wed, 04 Oct 2023 12:03:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696446224; x=1697051024; darn=lists.postgresql.org; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:to:from:from:to:cc:subject:date:message-id :reply-to; bh=bo0LQ91IysB/i8bjV8uf/zT+cLWELyE/PPz2dXCNHoI=; b=dr2ZCvg56s9FUK6jdnlBrf9IA8Wlw2juNfthrHGRADAeU8JWz+WwAEyO1w5n518XOW iQDHg0+4bbxVoEEry/zYc3bx7XVDXNDJeJ4CrviTCP0wym1wmRk6oMPqLjcv8EmJym3d bnTJD+M87DAweOaMw9LAPgZn8TMNzgU5X8xzIqMaXOKXvEEic/SNzdRElME48oJ9TAuX F/hx0U3/MvnGJyX8B62+msGb/S8RGT9m07d5M6hTSGbhDVwqFyy7UymdSa9IfPxCkG0d dALBUEmi9AM5HgnOr8UYno20cIeTR56468AfSyrzVFUyj7C3YpIzBHu7uNFiEhyhUCOJ bBpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696446224; x=1697051024; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=bo0LQ91IysB/i8bjV8uf/zT+cLWELyE/PPz2dXCNHoI=; b=QqEfSSxfVvA4ry3hlt/aakdzFnPGWJhiNDJh57ZUNovVOD5ciWyccTIixH33iFmAqs SsJxLqxLbf4j+lnb8wo6hDg1cp98So5R4ULga+3VGbBslsT94MW2e1kxAQ/uBrgZdiSm y58RBYEz8YWR7o2XWCfRopP2jK5rtl0Q2ZezV52z5/TAMsS2BfbzTk10sLIeYsCSTwh4 ONw3LP7n2782wD3u0Srn6IWw63KT00OQbd09BYMg1LwQKStty8RmX2TF6C55PU1O7wdS gYbGlBE6gHw/zo9js8rxuOs/5usC4HCUWX0gsqrl0ktMc6bSdvc0Z87od62bhYm3BNa+ goFQ== X-Gm-Message-State: AOJu0YzRRewhmYN0GHClnrOuwhh0Lo0OpNRT9GIsB4NWvEudp2L3M1K9 1L4lcIwDcdrXdlF0YeVdB50B+rXz8gHL9jo9gKw= X-Google-Smtp-Source: AGHT+IFgWpd4xy5dRqk54w0eIDt3x4hEOjKlyoCvRavUJO9QOsw9InxsDZFBKbmL9HmguRrowLEgig== X-Received: by 2002:a1c:7419:0:b0:406:7d74:a2a6 with SMTP id p25-20020a1c7419000000b004067d74a2a6mr3128473wmc.24.1696446224224; Wed, 04 Oct 2023 12:03:44 -0700 (PDT) Received: from ISBLT2102 ([206.84.151.37]) by smtp.gmail.com with ESMTPSA id 17-20020a05600c231100b00402ff8d6086sm2168102wmo.18.2023.10.04.12.03.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Oct 2023 12:03:43 -0700 (PDT) From: To: "'SOzcn'" , References: In-Reply-To: Subject: RE: Timeout Issue Date: Wed, 4 Oct 2023 12:03:39 -0700 Message-ID: <003201d9f6f5$7d741400$785c3c00$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01D9F6BA.D11785F0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQI9ito8v7H8re/0fqK+TB3x3aAYDq9y02Jg Content-Language: en-us List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_0033_01D9F6BA.D11785F0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, =20 What is your current statement_timeout?, I want to suggest to for SET = statement_timeout =3D 60000; -- 60 seconds. =20 You can run the ANALYZE and VACUUM commands to optimize the table. =20 Regards, Tayyab =20 =20 =20 =20 =20 From: SOzcn =20 Sent: Wednesday, October 4, 2023 11:14 AM To: pgsql-admin@lists.postgresql.org Subject: Timeout Issue =20 Hello, I am getting an error like the one below in a cluster.=20 =3D=3DSQL Error [57014]: ERROR: canceling statement due to statement = timeout =20 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.=20 Like changing the index name and trying to instantly delete it.=20 I stopped all applications connected to the database and tried again. = But the result was the same.=20 I did not understand how I got this error even though there was no = session. =20 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. =20 I using Postgresql v13.9=20 2023-10-04 18:32:56.669 +03 [1339952] [user=3Duser,db=3Ddbname=3DDBeaver = 21.2.1 - SQLEditor ] ERROR: canceling statement due to = statement timeout 2023-10-04 18:32:56.669 +03 [1339952] = [user=3Duser,db=3Ddbname,app=3DDBeaver 21.2.1 - SQLEditor ] = STATEMENT: drop index dbname."indexname" Any advice? ------=_NextPart_000_0033_01D9F6BA.D11785F0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello,

 

What is your = current statement_timeout?, I want to suggest to for SET = statement_timeout =3D 60000; -- 60 seconds.

 

You can run = the ANALYZE and VACUUM commands to optimize the table.

 

Regards,

Tayyab

 

 

 

 

 

From: SOzcn = <selahattinozcnma@gmail.com>
Sent: Wednesday, October = 4, 2023 11:14 AM
To: = pgsql-admin@lists.postgresql.org
Subject: Timeout = Issue

 

Hello, = I am getting an error like the one below in a = cluster. 

=3D=3DSQL 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=3Duser,db=3Ddbname=3DDBeaver 21.2.1 - = SQLEditor <Console>] ERROR:  canceling statement due to = statement timeout

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

Any = advice?

------=_NextPart_000_0033_01D9F6BA.D11785F0--