| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ashwiththatipally(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19387: About Response time delay. |
| Date: | 2026-01-23 15:16:49 |
| Message-ID: | 3104686.1769181409@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> When using PostgreSQL 18.1 on macOS, I am experiencing severe response time
> delays, including:
> A 3–5 second delay between typing characters and their appearance in the
> query editor/terminal.
> Very slow application startup, taking nearly 2 minutes to open and become
> responsive.
> Overall high latency and performance degradation during basic interactions.
Nobody else has reported any such thing. We do have a lot of PG
developers (including me) who use macOS regularly, so if there were a
generic problem of this sort I'm pretty sure we'd have heard about it.
In any case, we can't really investigate something we can't reproduce.
I suppose your problem is with the client side, since the PG server
wouldn't normally be involved in echoing individual characters.
If you're using pgAdmin, there's a separate bug reporting process
for that (this list is just about bugs in the core PG software).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-01-23 15:35:45 | Re: BUG #19388: Failing to connect to postgres with EACCES error |
| Previous Message | PG Bug reporting form | 2026-01-23 13:37:08 | BUG #19388: Failing to connect to postgres with EACCES error |