public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Enrico Schenone <[email protected]>
To: [email protected]
Cc: Massimo Catti <[email protected]>
Cc: Livio Pizzolo <[email protected]>
Subject: Re: Intermittent errors when fetching cursor rows on PostgreSQL 16
Date: Fri, 20 Dec 2024 08:41:54 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 12/19/24 23:57, Enrico Schenone wrote:
> At 19/12/24 22:47, Adrian Klaver wrote:
>>
>>

>> So are they building their own driver over libpq?
> I think so.
> They wrote ...
> <
> 
> /The error “no connection to the server“ is definitively a PostgreSQL 
> error:/
> 
> /||/
> /|./src/interfaces/libpq/fe-exec.c: libpq_append_conn_error(conn, "no 
> connection to the server");|/
> 
> /It is not normal that PostgreSQL client can connect to the server, do 
> some SQL with success and then the SQL connection gets dropped at the 
> next SQL statement execution. This is really suspicious./

They must work in a perfect world where networks never fail. One that 
would render the blog below unneeded:

https://www.cybertec-postgresql.com/en/tcp-keepalive-for-a-better-postgresql-experience/

> 
>  >
> 

>>
> Best regards.
> Enrico

-- 
Adrian Klaver
[email protected]

view thread (15+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Intermittent errors when fetching cursor rows on PostgreSQL 16
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox