Re: Fwd: libpq: indefinite block on poll during network problems

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitry Samonenko <shreddingwork(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Fwd: libpq: indefinite block on poll during network problems
Date: 2014-05-30 17:46:33
Message-ID: 6395.1401471993@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dmitry Samonenko <shreddingwork(at)gmail(dot)com> writes:
> Yeah, that will work. Looks simple to implement in the client. Question is:
> why don't you think it should be a part of the libpq's API? It's a must
> have feature in high availability environments where only several minutes
> of Out of Service per year are tolerable.

That argument seems nonsensical from here. If you need HA then you should
be using network service monitoring tools, not relying on some random
libpq client to decide that its connection has been lost.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edoardo Panfili 2014-05-30 17:56:09 Re: unable to build postgres-9.4 in os x 10.9 with python
Previous Message Dmitry Samonenko 2014-05-30 17:39:36 Re: Fwd: libpq: indefinite block on poll during network problems