Re: libpq - prevent automatic reconnect
От | Chris Angelico |
---|---|
Тема | Re: libpq - prevent automatic reconnect |
Дата | |
Msg-id | CAPTjJmqcWP6iVrpGa+we+CY-vKOV8iYZO+sJd9KP0fizHnv_oA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: libpq - prevent automatic reconnect (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: libpq - prevent automatic reconnect
|
Список | pgsql-general |
On Thu, Dec 6, 2012 at 5:56 AM, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-general по дате отправления: