Re: Implementing setQueryTimeout() - round 2
От | Kris Jurka |
---|---|
Тема | Re: Implementing setQueryTimeout() - round 2 |
Дата | |
Msg-id | Pine.BSO.4.64.0802190453130.8772@leary.csoft.net обсуждение исходный текст |
Ответ на | Re: Implementing setQueryTimeout() - round 2 (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: Implementing setQueryTimeout() - round 2
|
Список | pgsql-jdbc |
On Tue, 19 Feb 2008, Oliver Jowett wrote: > Add 4 new connection parameters, associated connection / statement values and > accessors on the postgresql extension interfaces: > > - softQueryTimeout: 0=disabled, >0 = timeout in ms, default 0 > - hardQueryTimeout: 0=disabled, >0 = timeout in ms, default 0 > - softQueryMargin: -1=disabled, >=0 = margin in ms, default 0 > - hardQueryMargin: -1=disabled, >=0 = margin in ms, default 60s > > Any comments on this iteration? Too configurable? Not configurable enough? > Are the defaults sensible? > Sounds too configurable. I don't understand the use case for softQueryMargin at all right now. Since hardQueryTimeout + hardQueryMargin should be > softQueryTimeout + softQueryMargin for a reasonable configuration, we don't need all these parameters. Don't you just want: 1) defaultQueryTimeout: 0=disabled, >0 timeout in ms 2) hardTimeoutMargin: -1 disabled, >=0 hard timeout above query timeout Kris Jurka
В списке pgsql-jdbc по дате отправления: