Re: Statement timeout - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Statement timeout
Date
Msg-id CAA4eK1+tX-TOBx-XNrrSFtnezGZOwory+An75dthZknjVYc_MQ@mail.gmail.com
Whole thread Raw
In response to Re: Statement timeout  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
On Wed, Jun 1, 2016 at 6:03 AM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>
> From the document about statement_timeout (config.sgml):
>
>         Abort any statement that takes more than the specified number of
>         milliseconds, starting from the time the command arrives at the server
>         from the client.  If <varname>log_min_error_statement</> is set to
>         <literal>ERROR</> or lower, the statement that timed out will also be
>         logged.  A value of zero (the default) turns this off.
>
> Apparently "starting from the time the command arrives at the server
> from the client" referrers to the timing of execute message arrives to
> server the in my example. And I think current behavior of our code is
> doing different from what he document advertises. Or at least counter
> intuitive to users.
>

It seems to me the above documentation is more relevant with respect to simple query.  However, I agree that it is better if statement_timeout is the timeout for each execution of the parsed statement.


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: Question and suggestion about application binary compatibility policy
Next
From: Robert Haas
Date:
Subject: Re: Rename max_parallel_degree?