Re: libpq: indefinite block on poll during network problems

From: Dmitry Samonenko <shreddingwork(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: libpq: indefinite block on poll during network problems
Date: 2014-05-30 21:06:42
Message-ID: CAFKp+3c8tUO-NNgk0uCKd9-X0PnabB2de_sLwM__qpLR0Lzd8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sorry, my last mail got truncated. I'm starting to like Gmail mobile.

On Saturday, May 31, 2014, Dmitry Samonenko <shreddingwork(at)gmail(dot)com> wrote:
>
>
>> Though this then begs the question: if the connection comes back up what
>> happens in the client?
>
>
>
>> Depends on the state of the server. If problem was purely network related
> - TCP retransmit eventually
>
succeeds and client gets reply (with pause of course). Normal client
operation resumes. If the server has crashed and the client hasn't received
FIN segment (hardware crash for example), then the client is doomed for TCP
retransmission retries.

>
> If the client is still stuck then I'd say that is
>> possibly our problem to address - but if the client resumes then expecting
>> and resolving the issue at a higher level seems to make sensible policy.
>>
>> David J.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://postgresql.1045698.n5.nabble.com/libpq-indefinite-block-on-poll-during-network-problems-tp5805061p5805605.html
>> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>>
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kapil Agarwal 2014-05-30 22:19:26 Re: Archive# views
Previous Message Dmitry Samonenko 2014-05-30 21:00:30 Re: libpq: indefinite block on poll during network problems