public inbox for [email protected]  

help / color / mirror / Atom feed

From: Aislan Luiz Wendling <[email protected]>
To: Scott Ribe <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: debug a lockup
Date: Wed, 11 Feb 2026 00:00:43 +0000
Message-ID: <SN7P223MB05809AA60554BD2253269B6DDD62A@SN7P223MB0580.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Hello,

Does it repeat on every run?

If it is possible, try to gracefully stop postgresql.

Not working? Try stop immediate and last resort stop abort.

If postgrres service does not stop, try to kill pgbench process.
First try kill -15 <pgbench PID> and if it does not work, kill -9

Nothing works, reboot the vm.

Open two terminals, start pgbench process in one. In the other ps -ef | grep pgbench

Find the parent process ID and do a strace -f -p <PID> (maybe your kernel has a different syntax, but it is to trace a process and its forks)

It can show which set of instructions is waiting. You will know because usually you are not able to read due to its speed, but when it stops, it is waiting for something.


Hope it helps.

ALW
________________________________
From: Scott Ribe <[email protected]>
Sent: Tuesday, February 10, 2026 11:55 AM
To: Pgsql-admin <[email protected]>
Subject: debug a lockup

PostgreSQL appears locked up. pgbench run that should have completed in a few seconds has been running  14 hours. psql invocation locks up. No CPU usage showing in top.

I personally suspect infra issues. (k8s pod, Pure block storage) But I'm getting pushback pointing the finger at PG. It's 18.1, and pgbench is the only client FWIW.

Any way to introspect the current non-debug build to get a clue what's going on in there?

--
Scott Ribe
[email protected]
https://www.linkedin.com/in/scottribe/

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: debug a lockup
  In-Reply-To: <SN7P223MB05809AA60554BD2253269B6DDD62A@SN7P223MB0580.NAMP223.PROD.OUTLOOK.COM>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox