MIME-Version: 1.0
References: <CACgMzfwJQy8QmOFWdb3B1QNBchxC=4PjpBYMk4zgQz_WY8qmLQ@mail.gmail.com>
 <69982fc8a6ea2b7c2030d8206e16a8af081e7c46.camel@cybertec.at> <CACgMzfx0m=R8QrvQ19+AOv6Y6eu31bqp+881mzAdX8rK28ggyQ@mail.gmail.com>
In-Reply-To: <CACgMzfx0m=R8QrvQ19+AOv6Y6eu31bqp+881mzAdX8rK28ggyQ@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Mon, 10 Nov 2025 09:34:13 -0500
Message-ID: <CAKAnmm+A90ASkLETXVq8Yc1xs4JqOBY0W055t_fES-JVJWxT0w@mail.gmail.com>
Subject: Re: Enquiry about long-running queries
To: Ashish Mukherjee <ashish.mukherjee@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b8734806433e6e05"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BA90ASkLETXVq8Yc1xs4JqOBY0W055t_fES-JVJWxT0w%40mail.gmail.com>
Precedence: bulk

--000000000000b8734806433e6e05
Content-Type: text/plain; charset="UTF-8"

Wow, 9 days is a long time. The fact that it is not responding to
pg_terminate_backend means it's not even calling CHECK_FOR_INTERRUPTS
inside the WaitForParallelWorkersToFinish loop, so something is seriously
wrong. If the PID is still there, please do what Laurenz suggested:

strace -tp 356274

Is the problem reproducible, and has it happened more than once?

Cheers,
Greg

--000000000000b8734806433e6e05
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Wow, 9 days is a long time. The fact that it is not respon=
ding to pg_terminate_backend means it&#39;s not even calling CHECK_FOR_INTE=
RRUPTS inside the=C2=A0WaitForParallelWorkersToFinish loop, so something is=
 seriously wrong. If the PID is still there, please do what Laurenz suggest=
ed:<div><br></div><div>strace -tp 356274</div><div><br></div><div>Is the pr=
oblem reproducible, and has it happened more than once?</div><div><br></div=
>Cheers,<div>Greg</div><div><div><div><br></div><div><br></div><div><br></d=
iv><div><br></div></div></div></div>

--000000000000b8734806433e6e05--