public inbox for [email protected]  

help / color / mirror / Atom feed

From: Scott Ribe <[email protected]>
To: Aislan Luiz Wendling <[email protected]>
To: Tom Lane <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: debug a lockup
Date: Tue, 10 Feb 2026 17:12:19 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <SN7P223MB05809AA60554BD2253269B6DDD62A@SN7P223MB0580.NAMP223.PROD.OUTLOOK.COM>
References: <[email protected]>
	<SN7P223MB05809AA60554BD2253269B6DDD62A@SN7P223MB0580.NAMP223.PROD.OUTLOOK.COM>

OK, we figured it out--I think.

pgbench was stuck in restart_syscall(<...resuming interrupted read...

it was set to open 100 connections

there were ~20 pg sessions in idle, and the last one (highest pid) in auth

that one was in write to fd 2

So... This is running in kubernetes. I was doing some load testing against a storage service (thus 100 connections). PG was launched manually in a bash session connected to the pod, in k9s. There were ~20 total bash sessions open in k9s across 15 nodes.

Theory: k9s glitched and stopped reading the piped file descriptor, buffer filled, and PG blocked on the write. (I have seen prior evidence of less-than-perfect handling of output by k9s). Particularly, I had logging of connections on, so at auth it would have been writing to stderr.

This happened in one of probably over 100 runs of the same test, so not readily reproducible and I wanted to autopsy it before killing off the hung processes. Unless someone pokes a hole in my theory, at this point I think it is neither pgbench nor PG nor Pure/Portworx at fault.

--
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], [email protected]
  Subject: Re: debug a lockup
  In-Reply-To: <[email protected]>

* 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