Обсуждение: BUG #16674: The idle connection get created automatically
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?
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.
already we tried with this "pg_stat_activity" and the IPaddress is the same as the server address and it's called from internally in the postgres.so we suspect its a bug.
On Fri, 16 Oct 2020 at 19:53, David G. Johnston <david.g.johnston@gmail.com> wrote:
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.
Thanks & Regards,
SathisH R,Development Team,
Eazy Business Solutions.
On Sunday, October 18, 2020, Sathish R <sathishR@eazyerp.com> wrote:
already we tried with this "pg_stat_activity" and the IPaddress is the same as the server address and it's called from internally in the postgres.so we suspect its a bug.
Nothing in the core PostgreSQL products is doing what you describe. If it is a bug it’s not ours. If you want help researching/debugging this using the tools provided by PostgreSQL that is best done on the -general list. Regardless, you need to identify which third-party project is responsible and inform them.
David J.
On Friday, October 16, 2020, PG Bug reporting form <noreply@postgresql.org> wrote:
We are using the postgreSQL 11.3 and 9.4 version in windows server 2012 and
Linux servers.
Frankly, you should update to latest supported version before reporting bugs/problems. Or at least attempt a reproducer in a test environment using the latest version.
David J.
Thanks, I'll check it out.
On Mon, 19 Oct, 2020, 12:04 pm David G. Johnston, <david.g.johnston@gmail.com> wrote:
On Friday, October 16, 2020, PG Bug reporting form <noreply@postgresql.org> wrote:
We are using the postgreSQL 11.3 and 9.4 version in windows server 2012 and
Linux servers.Frankly, you should update to latest supported version before reporting bugs/problems. Or at least attempt a reproducer in a test environment using the latest version.David J.