From: | "yanliang lei" <msdnchina(at)163(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re:Re: suggestion about statement_timeout |
Date: | 2024-09-01 13:38:04 |
Message-ID: | 9808b0e.2a6d.191adce9ae7.Coremail.msdnchina@163.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
I got it。
thanks a lot
在 2024-09-01 11:48:33,"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> 写道:
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 | PG Doc comments form | 2024-09-02 10:16:06 | retrieving results of procedures with OUT params |
Previous Message | David G. Johnston | 2024-09-01 03:48:33 | Re: suggestion about statement_timeout |