You might have better luck asking on the pgsql-general mailing list
(you'll want to subscribe to it at http://archives.postgresql.org/).
I don't know if the windows hackers regularly read -bugs.
On Jul 14, 2008, at 4:14 AM, Alexandre wrote:
The following bug has been logged online:
Bug re
On Mon, Jul 14, 2008 at 5:14 AM, Alexandre <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4303
> Logged by: Alexandre
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2
> Operating system: Windows xp
> Description:i
"K, Niranjan (NSN - IN/Bangalore)" <[EMAIL PROTECTED]> writes:
> Is there any other workaround or alternative so that the situation about
> the interface is down is known and based on that the 'PQexec' does not
> get blocked for ~15 minutes.
Absent threads I think you have to use alarm() and a SI
Gregory Stark <[EMAIL PROTECTED]> writes:
> "K, Niranjan (NSN - IN/Bangalore)" <[EMAIL PROTECTED]> writes:
>> Is there any other workaround or alternative so that the situation about
>> the interface is down is known and based on that the 'PQexec' does not
>> get blocked for ~15 minutes.
> Absent
I have noticed this as well. Blocks in poll(), timeout parameter -1, meaning
infinite then after 4 minutes on my system poll() returns 1 and
getsockopt() is called with SO_ERROR. SYN packets are tried only for the
default tcp timeout of 20 seconds.
Consider using threads that way you can set yo
"Valentin Bogdanov" <[EMAIL PROTECTED]> writes:
> I have noticed this as well. Blocks in poll(), timeout parameter -1,
Oh good point. non-blocking sockets and poll/select let you control the
timeout too.
> meaning infinite then after 4 minutes on my system poll() returns 1 and
> getsockopt() i
Thanks Gregory,
You right, of course, about that. It is 4 minutes I wasn't paying attention and
thought that I have found something odd. The last packet is sent a minute and a
half after the first and I miss-read that for 20 seconds.
Cheers,
Val
--- On Wed, 16/7/08, Gregory Stark <[EMAIL PROT
Thanks Gregory,
You right, of course, about that. It is 4 minutes I wasn't paying attention and
thought that I have found something odd. The last packet is sent a minute and a
half after the first and I miss-read that for 20 seconds.
Cheers,
Val
--- On Wed, 16/7/08, Gregory Stark <[EMAIL PROT
