| From: | Roberto Mello <roberto(dot)mello(at)gmail(dot)com> |
|---|---|
| To: | Srinivas Kumar <srinivasnerusu(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server |
| Date: | 2026-05-27 23:49:14 |
| Message-ID: | CAKz==bJx-xyOGNi3VA1-ib4n2mr2vccdUEpDhpSSQccFRFVzyg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 27, 2026 at 4:19 PM Srinivas Kumar <srinivasnerusu(at)gmail(dot)com>
wrote:
> Hello Tomas,
>
> Thanks for reaching out! For more details, users connect directly to
> PostgreSQL using the DBeaver tool. Please review the attached error
> messages in the PostgreSQL server logs, and the timeout error on the
> EDWDBPRDL01A server. We have another dev server in Windows, which works
> absolutely fine without this issue, as you can review. Please let me know
> if any more specific details are required.
>
From the logs you sent I don't see anything that jumps out.
- 58 lines total
- 6 connection authenticated
- 6 connection authorized
Only one problem: FATAL 08006 connection to client lost on PID 1994906
(pgAdmin -> EDW, 18:56:11). Preceded by LOG 08006 - could not send data to
client: Broken pipe. pgAdmin dropped the TCP socket while the session was
idle. Postgres detected it when it tried to write back. Client-side
disconnect, not a server error.
Everything else is normal: SETs, idle state transitions, and clean
disconnections. No auth failures, no query errors, no locks, no timeouts
recorded server-side.
Roberto
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Baji Shaik | 2026-05-27 23:51:50 | Re: [PATCH] Improve REPACK (CONCURRENTLY) error messages for unsupported configurations |
| Previous Message | Masahiko Sawada | 2026-05-27 23:28:13 | Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process |