Re: Enabling connection pooling by default

Поиск
Список
Период
Сортировка
От Adam M
Тема Re: Enabling connection pooling by default
Дата
Msg-id 84b37b360810161923o55bb14a0p96e6e7c9c43241e5@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Enabling connection pooling by default  ("Andrus" <kobruleht2@hot.ee>)
Ответы Re: Enabling connection pooling by default  ("Andrus" <kobruleht2@hot.ee>)
Список pgsql-odbc
On Wed, Oct 15, 2008 at 2:47 PM, Andrus <kobruleht2@hot.ee> wrote:
>> Aren't pulled connections going to suffer from the same disconnection
>> problems as nonpulled connections?
>
> No.
> Only idle connections seems to be killed automatically by ADSL modem.
> Maybe TCP_KEEPALIVE can fix this but I havent found any inforamtion about
> its usage with PostgreSQL.

If your ADSL modem is also your router, and you are using NAT, then it
is not killing your connection. It is merely removing it from active
connection queue after 3 min or so of no activity.

If your ADSL modem is not a router, and "disconnects" your connection,
then the ADSL modem is broken. If you have a NAT outside the modem,
then it is the NAT that is timing out, not the modem.

TCP_KEEPALIVE messages are only useful when you have a non-public IP
and/or using NAT and/or want PostgreSQL to close connections where the
client has disappeared.

- Adam

В списке pgsql-odbc по дате отправления:

Предыдущее
От: "Andrus"
Дата:
Сообщение: Re: Enabling connection pooling by default
Следующее
От: salman Sheikh
Дата:
Сообщение: Error in Adding All Table