![]() ![]() ![]() once per minute should have minimal impact. However, I assume that sending a single command to the server eg. Without Keep-Alive, Postico wouldn't ever know that we drove through a tunnel)Īnother disadvantage of Keep-Alives is that Postico would need to periodically run code, increasing idle CPU usage. If Postico tries to send a Keep-Alive query while the train is in the tunnel, it will think the connection is lost, and I will need to reconnect later. There is no connection inside the tunnel. (Real Live Example: I'm on a train, entering a tunnel. There is a potential downside to a Keep-Alive mechanism: If you have an unreliable connection with intermittent connectivity, Postico will close the connection, even if the connection issues are only temporary. by sending a no-op query like SELECT 1 to the PostgreSQL server - this way we can be sure everything works. If you use a compiler newer than version 11.x, you can use the release option to specify that the target version is version 11. I think the best way to implement it is on the highest level, ie. To create a JAR file that contains the compiled Java code: Use javac to compile your. Such a keep-alive can be implemented on various levels (TCP, SSH, PostgreSQL). This would ensure that connections aren't dropped by over-protective firewalls, and it would also allow Postico to detect a lost connection more quickly. I believe the best way to go forward is to add a Keep-Alive mechanism to Postico. I've tried to address this issue by adding a setting that preemptively disconnects from the server after a period of inactivity, but that has been causing issues with temporary tables and settings like search_path ( #142). Reducing timeouts is not really an option, since it would cause issues when using Postico over slow connections. ![]() This is especially true for SSH connections ( #66). However, sometimes it can take a long time for Postico to detect that a connection is lost. Postico reconnects automatically when the connection is lost. This can be caused by a number of reasons a possible cause are Firewalls that automatically drop idle connections. A couple of users have reported issues that the connection drops after a certain time of inactivity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |