From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | yanliang lei <msdnchina(at)163(dot)com> |
Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: suggestion about statement_timeout |
Date: | 2024-09-01 03:48:33 |
Message-ID: | CAKFQuwZVjFjHQkRG9K5o9mBkyqP+3MouwwN+TYQeHqPBs0oecw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Saturday, August 31, 2024, yanliang lei <msdnchina(at)163(dot)com> wrote:
> hi,
> in the https://techcommunity.microsoft.com/t5/azure-
> database-for-postgresql/connection-handling-best-
> practice-with-postgresql/ba-p/790883
> there is the following description:
> alter database dbnamehere set statement_timeout = 60000;
>
>
> but the the https://www.postgresql.org/docs/current/runtime-
> config-client.html
> where is no description that statement_timeout can be used at the database
> level
>
> so,i suggestion:adding some description that statement_timeout can be
> used at the database level
>
All client connection default settings can be attached to either a role, a
database, or both. In fact, the majority of settings can, and so unless
stated otherwise, the guidance in 20.1.3 is meant to be taken as being
applicable. And in any case, this particular setting is in no way special
should one wish to suggest a concrete change.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | yanliang lei | 2024-09-01 13:38:04 | Re:Re: suggestion about statement_timeout |
Previous Message | yanliang lei | 2024-09-01 03:36:44 | suggestion about statement_timeout |