Re: connect_timeout parameter in libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Denis A Ustimenko <denis(at)oldham(dot)ru>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: connect_timeout parameter in libpq
Date: 2002-08-13 03:35:17
Message-ID: 21712.1029209717@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Denis A Ustimenko <denis(at)oldham(dot)ru> writes:
> I need to change current connectDBComplete() behavior ( hang if
> backend are not responding). Here is the patch. Please apply.

Shouldn't such a patch include documentation updates? (And not
only user-level documentation; this patch adds not even a single
comment to explain what it's doing or why.)

I'm also not thrilled with the way that the patch imposes the
overhead of calculating the timeout whether the user wants it or not.
The time() kernel calls should be skipped unless needed.

A final comment is that the patch's timeout accuracy is quite poor, since
time()'s result is quantized to seconds. gettimeofday() might be a
better choice. Also it seems to assume that select() does not modify its
timeout argument, which is not a portable assumption. On some platforms
the timeout struct is decremented by the elapsed time.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Gavin Sherry 2002-08-13 04:12:15 Re: Fix disabled triggers with deferred constraints
Previous Message Denis A Ustimenko 2002-08-13 02:54:11 connect_timeout parameter in libpq