This parameter is supported only on systems that support the TCP_KEEPIDLE or TCP_KEEPALIVE symbols, and on Windows Keep in mind the remark in the documentation: The keepalive message should avoid the NAT connection begin dropped. In sessions connected via a Unix-domain socket, this parameter is ignored and always reads as zero. This parameter is supported only on systems that support the TCP_KEEPIDLE or TCP_KEEPALIVE symbols, and on Windows on other systems, it must be zero. Specifies the number of seconds of inactivity after which TCP should send a keepalive message to the client. To do that: change one server parameter, called tcp_keep_alives:Īccording to the PostgreSQL documentation on Connections: Make the router believe the connection is never idle for long enough. If this is the case, you have three options:Ĭhange the connection_timeout setting in your router, if that is feasible and you have the proper documentation. It is not something done by neither pgAdmin nor PostgreSQL, this is something that depends on the settings on the router, After some idle time the connection is closed by the router. This is quite common when you are at home (or in the office) and your router is performing NAT ( Network Address Translation). I would think that the problem might be related to a router (or, in some cases, a stateful firewall) between your pgAdmin client and the PostgreSQL server. PgAdmin keeps throwing up a connection timeout every 10 minutes or so. Given the fact I already had one answer in place, I (not very humbly) think it is worth "asking", in case the answer is helpful to someone. It is spin-off of another one, that ended up not being related to loss of connectivity. What can be done it to avoid pgAdmin from disconnecting from the database?ĭisclosure: This is actually a "pseudo-question". (There seems to be ways to change some connection timeouts, but they're related to how pgAdmin behaves with regard to the server taking too long to connect). PgAdmin doesn't seem to have any parameter related to that behaviour. Do you want me to try to reconnect?"Īnd pgAdmin reconnects always need more than one trial, and the object-tree that was already expanded gets collapsed. One coffee and one phone call, and you get a message similar to "Sorry, connection to database is lost. When working with pgAdmin 4 (and actually, several other programs that act as clients to the database), the connection to the server disconnects after some 10 or 15 minutes of inactivity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |