| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jeremy(dot)spriet(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart |
| Date: | 2025-06-25 05:36:35 |
| Message-ID: | bca411e1abe036fd5fbb7f5ca3012c9d1c957604.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, 2025-06-24 at 15:09 -0400, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > I’m running PostgreSQL 16.9 in Docker (PostgreSQL 16.9 (Debian
> > 16.9-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc 12.2.0, 64-bit),
> > and intermittently observe that invalid SQL queries hang indefinitely
> > instead of immediately returning an error.
> > Valid queries continue to work normally and return results right away.
>
> You've not provided nearly enough info to do more than
> speculate, however.
Yes. One speculation that occurs to me is that the control group settings
of your container are such that a process that exceeds the memory quota is
suspended until enough memory becomes free.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-06-25 06:15:23 | BUG #18969: security tests failures |
| Previous Message | Daniil Davydov | 2025-06-25 04:04:10 | Re: BUG #16961: Could not access status of transaction |