| From: | Chris Angelico <rosuav(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: libpq - prevent automatic reconnect |
| Date: | 2012-12-06 21:43:58 |
| Message-ID: | CAPTjJmqcWP6iVrpGa+we+CY-vKOV8iYZO+sJd9KP0fizHnv_oA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Dec 6, 2012 at 5:56 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I suspect this action isn't dropping the TCP connection. It's only
> equivalent to a momentary glitch in your network connectivity --- and
> you'd be very unhappy if that caused TCP connections to go down, because
> networks have glitches all the time. Generally, the operating system
> tries hard to prevent applications from even knowing that a glitch
> happened. (Connections will time out eventually if connectivity doesn't
> come back, but typically such timeouts are many minutes. Possibly
> whatever your real complaint is could be addressed by twiddling the TCP
> timeout parameters for the socket.)
Yep. For a better test, try taking the interface down for a good while
(several minutes), or actually shut down the Postgres server at the
other end.
ChrisA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2012-12-06 21:51:47 | Re: unlooged tables |
| Previous Message | Adrian Klaver | 2012-12-06 20:25:29 | Re: Trigger / constraint issue |