Closing PostgreSQL in Application engine

romer-biscocho

Hello community,

We currently have a customer who is migrating from v11 to v12. To do this they need to replace their ImportMaster scripts with Application Engine scripts.
They are using a PostgreSQL database. Our customer now has the following problem. In their script they open a connection to their database.
At the end they close all PostgreSQL connections and they also release all preparedcommands.

Even though they do all this, the query still seems to be active on the database and it is taking up memory. Apparently in ImportMaster the connections were closed with a specific command and it did work,
but using the disconnect/release command or the using statement block in Application Engine does not seem to work.

Does anyone have experience with PostgreSQL connections in Application Engine and have you encountered the same problem?

Any help or advice would be greatly appreciated.

Best regards.
Romer

ivan-rebo

Please contact support and see if you can help them replicate it with smallest process possible including a way to check on Postgre side whether the connection is still open.

One idea would be that its related to connection pooling so it reuses the old connection on new reconnect and only would close the connection after some time...