Re: System Query hit to Database

I have already answered that 2 days ago:

This is the query sent by getTables() (as mention on Stackoverflow).

There are some connection pools out there that have a stupid default configuration and use getTables() as the query to validate if a connection is still alive. If you additionally have enabled validating connections when they are taken out or returned to the pool, this will be called for each "getConnection()" inside your code.

Check the configuration of your connection pool.

dhaval jaiswal schrieb am 13.02.2016 um 11:53:
> Can anyone help me on below query.
>
>
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> *From:* dhaval jaiswal <dhavallj(at)hotmail(dot)com>
> *Sent:* Thursday, February 11, 2016 10:32 AM
> *To:* pgsql-jdbc(at)postgresql(dot)org
> *Subject:* System Query hit to Database
>
> Kindly redirect me to the correct forum, If below question is not relevant to you.
>
>
>
> I am getting lot of following queries on my Database. I need your help to stop hitting this kind of queries to database.
>
> While going through search found the following article saying it's caused by jdbc driver.
>
> http://stackoverflow.com/questions/5453992/a-very-strange-sql-of-postgresql
>
> Environment details:
>
> Version: PostgreSQL 9.4.0
>
> Driver version: postgresql-9.4-1201.jdbc41.jar
>
> JVM: 1.7
>
>
>