Re: Support millisecond accuracy for timeouts
| От | Stevo Slavić |
|---|---|
| Тема | Re: Support millisecond accuracy for timeouts |
| Дата | |
| Msg-id | CAAUywg9ZYBkUStZKB4h5WjTCxaY6_gKkuxLURWMYuK8_WiXKLw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Support millisecond accuracy for timeouts (Oliver Jowett <oliver@opencloud.com>) |
| Ответы |
Re: Support millisecond accuracy for timeouts
|
| Список | pgsql-jdbc |
Hello Oliver,
Thanks for quick reply! I didn't look in the code, relied on docs I referenced and they specify following:
{quote}
loginTimeout = int
Specify how long to wait for establishment of a database connection. The timeout is specified in seconds.
{quote}
Docs are similar for socketTimeout.
Will have a look in the code.
Regards,
Stevo.
Thanks for quick reply! I didn't look in the code, relied on docs I referenced and they specify following:
{quote}
loginTimeout = int
Specify how long to wait for establishment of a database connection. The timeout is specified in seconds.
{quote}
Docs are similar for socketTimeout.
Will have a look in the code.
Regards,
Stevo.
On Thu, Nov 24, 2011 at 8:22 PM, Oliver Jowett <oliver@opencloud.com> wrote:
On 25 November 2011 16:07, Stevo Slavić <sslavic@gmail.com> wrote:loginTimeout should already support fractional values; what are you
> loginTimeout and socketTimeout connection parameters (
> http://jdbc.postgresql.org/documentation/head/connect.html#connection-parameters
> ) seem to be at 1 second accuracy. Could this be improved to support
> millisecond accuracy? Would like to configure these timeouts at value lower
> then a second.
seeing that makes you think it has whole-second resolution?
socketTimeout looks like a small change to do the same (parse as float
and scale to milliseconds), maybe you can send a patch for that?
Oliver
В списке pgsql-jdbc по дате отправления: