{"action":"opened","issue":{"url":"https://api.github.com/repos/brianc/node-postgres/issues/1627","repository_url":"https://api.github.com/repos/brianc/node-postgres","labels_url":"https://api.github.com/repos/brianc/node-postgres/issues/1627/labels{/name}","comments_url":"https://api.github.com/repos/brianc/node-postgres/issues/1627/comments","events_url":"https://api.github.com/repos/brianc/node-postgres/issues/1627/events","html_url":"https://github.com/brianc/node-postgres/issues/1627","id":317734952,"number":1627,"title":"Too many open TCP connections with Azure Database for Postgres","user":{"login":"rahulbreddy","id":29210409,"avatar_url":"https://avatars2.githubusercontent.com/u/29210409?v=4","gravatar_id":"","url":"https://api.github.com/users/rahulbreddy","html_url":"https://github.com/rahulbreddy","followers_url":"https://api.github.com/users/rahulbreddy/followers","following_url":"https://api.github.com/users/rahulbreddy/following{/other_user}","gists_url":"https://api.github.com/users/rahulbreddy/gists{/gist_id}","starred_url":"https://api.github.com/users/rahulbreddy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rahulbreddy/subscriptions","organizations_url":"https://api.github.com/users/rahulbreddy/orgs","repos_url":"https://api.github.com/users/rahulbreddy/repos","events_url":"https://api.github.com/users/rahulbreddy/events{/privacy}","received_events_url":"https://api.github.com/users/rahulbreddy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-25T18:03:36Z","updated_at":"2018-04-25T18:03:36Z","closed_at":null,"author_association":"NONE","body":"Our application uses 7.4.1 version of pg with all default values. I tried the same application with a local postgres (versions 9.4 and 9.6) and postgres on AWS RDS (version 9.5.1). Both seems to work fine.\r\n\r\nHowever with Azure Database for Postgres, the number of open tcp connections on the client keep increasing. My application executes a couple of queries every minute and looks like the pg module terminates the connection after 30 sec of inactivity.\r\n\r\nOn my local postgres and postgres on aws, I see that the server acknowledges and sends a FIN signal when it receives an X from the client. However, Azure Database for Postgres sends a keepalive and the TCP connections are kept open forever.\r\n\r\nHas any one experienced this behavior?"}}
{"actor":{"display_login":"rahulbreddy"}}