| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Enrico Schenone <eschenone(at)cleistech(dot)it>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Cc: | Massimo Catti <mcatti(at)cleistech(dot)it>, Livio Pizzolo <lpizzolo(at)cleistech(dot)it> |
| Subject: | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |
| Date: | 2024-12-20 16:41:54 |
| Message-ID: | b6e184d5-1ae7-4f9e-a823-b697bdebbdc1@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-12-20 16:43:44 | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |
| Previous Message | Bharani SV-forum | 2024-12-20 16:09:56 | Re: cannot drop a tablespace which never exists in pg_tablespace |