Re: BUG #18133: Canceling statement due to statement timeout

I don't understand the reason for this lock when there is nothing running
in the background. I also provided simultaneous connection control.
However, there was no second session record in the database. PgAnalyze was
available as a 3rd party software, I used it a few months ago, and there
were requests from it, but I don't think it will lock the session. When I
experienced this problem before, I solved it by updating the "timeout"
parameters. However, now when I increase the statemant parameter, it runs
for a long time and when I check the log, it records as above.

PG Bug reporting form <noreply(at)postgresql(dot)org>, 25 Eyl 2023 Pzt, 13:27
tarihinde şunu yazdı:

> The following bug has been logged on the website:
>
> Bug reference: 18133
> Logged by: Selahattin Özcan
> Email address: selahattinozcnma(at)gmail(dot)com
> PostgreSQL version: 13.9
> Operating system: Ubuntu 20.04
> Description:
>
> Hello, I've been trying drop the index on the database and this error came
> up.
> I checked almost everything and as a last case, I asked to stop all API
> etc.; after that, I tried again, and the result didn't change.
>
> Example Logs;
> 2023-09-25 12:56:26.883 +03 [15780] LOG: received fast shutdown request
> 2023-09-25 12:56:26.884 +03 [15780] LOG: aborting any active transactions
> 2023-09-25 12:56:26.884 +03 [15952]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - SQLEditor
> <Console>] FATAL: terminating connection due to administrator command
> 2023-09-25 12:56:26.884 +03 [15921]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - Metadata
> <documentdb_earchive_igdas>] FATAL: terminating connection due to
> administrator command
> 2023-09-25 12:56:26.884 +03 [15919]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - Main
> <documentdb_earchive_igdas>] FATAL: terminating connection due to
> administrator command
> 2023-09-25 12:56:26.887 +03 [15780] LOG: background worker "logical
> replication launcher" (PID 15799) exited with exit code 1
> 2023-09-25 12:56:26.888 +03 [15794] LOG: shutting down
> 2023-09-25 12:56:26.945 +03 [15780] LOG: database system is shut down
> 2023-09-25 12:56:27.400 +03 [16504] LOG: starting PostgreSQL 13.9 (Ubuntu
> 13.9-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
> 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
> 2023-09-25 12:56:27.401 +03 [16504] LOG: listening on IPv4 address
> "0.0.0.0", port 5449
> 2023-09-25 12:56:27.401 +03 [16504] LOG: listening on IPv6 address "::",
> port 5449
> 2023-09-25 12:56:27.402 +03 [16504] LOG: listening on Unix socket
> "/var/run/postgresql/.s.PGSQL.5449"
> 2023-09-25 12:56:27.407 +03 [16513] LOG: database system was shut down at
> 2023-09-25 12:56:26 +03
> 2023-09-25 12:56:27.408 +03 [16513] LOG: recovering prepared transaction
> 101134325 from shared memory
> 2023-09-25 12:56:27.414 +03 [16504] LOG: database system is ready to
> accept
> connections
> 2023-09-25 12:57:08.348 +03 [16684]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - SQLEditor
> <Console>] ERROR: canceling statement due to statement timeout
> 2023-09-25 12:57:08.348 +03 [16684]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - SQLEditor
> <Console>] STATEMENT: drop index dbname."idname"
>
> ----
>
> 2023-09-25 13:23:04.848 +03 [27968]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - SQLEditor
> <Console>] ERROR: canceling statement due to statement timeout
> 2023-09-25 13:23:04.848 +03 [27968]
> [user=sozcan,db=documentdb_earchive_igdas,app=DBeaver 21.2.1 - SQLEditor
> <Console>] STATEMENT: DROP INDEX dbname."idname"
>
>