PostgreSql 9.4 Database connection failure

2021-09-09 Thread Lionel Napoleon
Hi,
  I have an issue with my PostgreSql 9.4 version database. Almost every 
week I get the following error

Error: #2147500037
Could not connect to the server;
Could not connect to remote socket immedaitely
Source: Microsoft OLE DB Provider for ODBC Drivers
SQL State: 08001

My application and database are on the same system. The communicating port 
being 5432.
initially I thought it was the permissible connection limit issue. So I raised 
the max_connections
parameter to 300.But still the problem exists.Would appreciate your speedy 
response to my
problem
Thanks & Regards
Lionel


Re: PostgreSql 9.4 Database connection failure

2021-09-09 Thread Ranier Vilela
Em qui., 9 de set. de 2021 às 04:46, Lionel Napoleon <
lionelnapol...@hotmail.com> escreveu:

> Hi,
>   I have an issue with my PostgreSql 9.4 version database. Almost
> every week I get the following error
>
> Error: #2147500037
> Could not connect to the server;
> Could not connect to remote socket immedaitely
> Source: Microsoft OLE DB Provider for ODBC Drivers
> SQL State: 08001
>
> My application and database are on the same system. The communicating port
> being 5432.
> initially I thought it was the permissible connection limit issue. So I
> raised the max_connections
> parameter to 300.But still the problem exists.
>
> I think that question will be better answered at:
https://www.postgresql.org/list/pgsql-general/

However, it seems to me that this is a bug with Microsoft ODBC.

regards,
Ranier Vilela


sql execution time in pg_stat_statements

2021-09-09 Thread Michel SALAIS
Hi all,

 

I think that total_time in pg_stat_statements is cpu time + possible waits.
So, can I say that:

Total_sql_time = total_time + blk_read_time + blk_write_time

 

Documentation is not clear at all on that.

 

Thanks in advance 

 

Michel SALAIS



RE: sql execution time in pg_stat_statements

2021-09-09 Thread Michel SALAIS
Just to say that for PostgreSQL 13, total_time is replaced by
“total_exec_time + total_plan_time”

 

Michel SALAIS

De : Michel SALAIS  
Envoyé : jeudi 9 septembre 2021 20:14
À : pgsql-performa...@postgresql.org
Objet : sql execution time in pg_stat_statements

 

Hi all,

 

I think that total_time in pg_stat_statements is cpu time + possible waits.
So, can I say that:

Total_sql_time = total_time + blk_read_time + blk_write_time

 

Documentation is not clear at all on that.

 

Thanks in advance 

 

Michel SALAIS



Re: sql execution time in pg_stat_statements

2021-09-09 Thread Julien Rouhaud
On Fri, Sep 10, 2021 at 2:49 AM Michel SALAIS  wrote:
>
> I think that total_time in pg_stat_statements is cpu time + possible waits. 
> So, can I say that:
>
> Total_sql_time = total_time + blk_read_time + blk_write_time
>
> Documentation is not clear at all on that.

In version 12 and below, total_time is the elapsed time between the
execution start and stop, so it includes all underlying events. That
includes any IO activity, wait events or nested statements (if
pg_stat_statemetns.track is set to all).  This corresponds to the new
total_exec_time field in version 13 and later.


> Just to say that for PostgreSQL 13, total_time is replaced by 
> “total_exec_time + total_plan_time”

Indeed, as this version also tracks planning activity.