From: Tom Lane <tgl@sss.pgh.pa.us>
To: teng_wang13@163.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17537: Dynamically updating statement_timeout not affect the insert query right now.
Date: Sun, 03 Jul 2022 11:01:20 -0400
Message-ID: <1216663.1656860480@sss.pgh.pa.us> (raw)
In-Reply-To: <17537-9c5b29383602bca0@postgresql.org>
References: <17537-9c5b29383602bca0@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> However, dynamically updating statement_timeout did not affect the insert
> query right now.
> I start up Postgres with statement_timeout set 0, which means disabling the
> timeout. Then I insert 100000000 rows into a table, which finally takes
> 166498.487ms. During the insert operation, I consider the operation would
> takes too much time. So I update statement_timeout to 10s in
> postgresql.conf, and "select pg_reload_conf();" in another session to reload
> configuration files.
This is not a bug. Active sessions absorb new values from postgresql.conf
only when idle, not instantaneously mid-query (and I'm pretty sure that is
documented, though I'm too lazy to search the docs right now). I think
trying to do the latter would break far more scenarios than it would
improve.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, teng_wang13@163.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17537: Dynamically updating statement_timeout not affect the insert query right now.
In-Reply-To: <1216663.1656860480@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox