Revision history [back]

There could be several reasons why the same query executed through JDBC takes an indefinite amount of time to run while it is completed in only one minute through pgAdmin. Some of the common reasons are:

1. Network Latency: If the JDBC client and the PostgreSQL server are located in different geographical locations, the network latency can cause delays in data transmission leading to slow query execution times.

2. JDBC Driver: The JDBC driver used to establish the connection between the client and the server could be outdated or incompatible, which could result in performance issues.

3. Client System Resources: The performance of the client system could also affect the query execution time. A system with insufficient resources like RAM, CPU, or disk space could lead to slow query execution times.

4. Connection Pooling: If the JDBC client is not using connection pooling, it could lead to slow query execution times as each query requires establishing a new connection to the server.

5. Query Optimization: It is possible that the same query is optimized differently by the JDBC client and pgAdmin. pgAdmin may be using cached results or may have a different execution plan for the same query, leading to faster execution times.