Re: BUG #16674: The idle connection get created automatically - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #16674: The idle connection get created automatically
Date
Msg-id CAKFQuwZTKEg11Ft6hp7nb1_DfBZ8KqrZspjzHbfZJWYbp3Loow@mail.gmail.com
Whole thread Raw
In response to BUG #16674: The idle connection get created automatically  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16674: The idle connection get created automatically
List pgsql-bugs
On Fri, Oct 16, 2020 at 4:01 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      16674
Logged by:          Sathish R
Email address:      sathishr@eazyerp.com
PostgreSQL version: 11.3
Operating system:   Windows
Description:       

We are using the postgreSQL 11.3 and 9.4 version in windows server 2012 and
Linux servers.

in windows server recently we are facing one issue and we couldn't find the
reason from our side. and same issue not faced in linux server.
the issue is automatically below mentioned queries are executed N number of
times in our server and connection limit get exceed.
Query: SELECT oid, (SELECT oid FROM pg_type WHERE typname like
''geography'') as dd  FROM pg_type WHERE typname like ''geometry''

we don't know how this query get fired and what is the purpose?

This form is for bug reports.  Kindly do not use it for non-bug questions.  The -general list is your best choice if one of the more specific lists doesn't not match the topic of your email closely.

Kinda looks like PostGIS if that helps.

You can use pg_stat_activity to figure out the ip addresses of the clients sending these queries then investigate those machines.

David J.

pgsql-bugs by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: BUG #16675: VALUES not working for CITEXT
Next
From: PG Bug reporting form
Date:
Subject: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return