From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>
cc: "MichaelDBA@sqlexec.com" <michaeldba@sqlexec.com>,
        PostgreSQL mailing lists <pgsql-performance@postgresql.org>
Subject: Re: query that canceled isnt logged
In-reply-to: 
 <CA+t6e1k+hP1tAVn=9u0-TxufrVZKEo2E2wBJ6X5BoCo1yKvm+g@mail.gmail.com>
References: 
 <CA+t6e1nYocLRyELmm6VM81JjfwTz_QbkiSJgyUkyDHGd-DFt8A@mail.gmail.com>
 <3160F744-01C9-4411-B1D2-36E737D6C2E5@sqlexec.com>
 <CA+t6e1k+hP1tAVn=9u0-TxufrVZKEo2E2wBJ6X5BoCo1yKvm+g@mail.gmail.com>
Comments: In-reply-to Mariel Cherkassky <mariel.cherkassky@gmail.com>
	message dated "Sun, 08 Dec 2019 17:18:37 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5942.1575819720.1@sss.pgh.pa.us>
Date: Sun, 08 Dec 2019 10:42:00 -0500
Message-ID: <5943.1575819720@sss.pgh.pa.us>
Precedence: bulk

Mariel Cherkassky <mariel.cherkassky@gmail.com> writes:
> If I'll try to run the following query and cancel it manually(ctrl+c) :
> select pg_sleep(10)
> I will see in the logs the following messages :

> 2019-12-08 17:16:34 IST postgres 30797  LOG:  statement: select
> pg_sleep(10);
> 2019-12-08 17:16:36 IST postgres 30797  ERROR:  canceling statement due to
> user request
> 2019-12-08 17:16:36 IST postgres 30797  STATEMENT:  select pg_sleep(10);

Note that that's going through "simple query" protocol (which is why
it says "statement:") but your application is evidently using "extended
query" protocol (because you see "execute ...:", at least when it's
working correctly).  I wonder whether the explanation is somewhere in
that.

The best theory I have at the moment, though, is that something is taking
exclusive locks on system catalogs, blocking parsing of even trivial
statements.

			regards, tom lane