pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrey Zhidenkov <pensnarik@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: PostgreSQL 15.5 stops processing user queries
Date: Thu, 21 Dec 2023 10:32:43 -0500
Message-ID: <657077.1703172763@sss.pgh.pa.us> (raw)
In-Reply-To: <CAN=gQ4A9Bq9=jri7qt8PUt4x7n576nZ6fqSpVx2DsdC=64uHeA@mail.gmail.com>
References: <CAN=gQ4A9Bq9=jri7qt8PUt4x7n576nZ6fqSpVx2DsdC=64uHeA@mail.gmail.com>

Andrey Zhidenkov <pensnarik@gmail.com> writes:
> We have encountered an issue with our PostgreSQL 15.5 installation. The
> problem is that
> PostgreSQL server periodically falls into a state when it accepts new
> connections but
> doesn't execute any queries. The session which runs a query hangs and
> cannot be terminated
> via SIGINT (even if it's just "SELECT 1") - a corresponding linux process
> has state "S" and it's
> not terminated even if the PostgreSQL master process is stopped. No matter
> how we connect to
> the database - both TCP and unix socket sessions hang but it seems that
> existing sessions can
> still execute queries (once we succeeded to connect using pgBouncer which
> seemed to use an
> existing connection to the database).

Try using an existing session to capture pg_stat_activity and pg_locks
information about the stuck session(s).

> Here is a stack trace from gdb for one of the frozen sessions:

This appears to be a trace of a psql process waiting for a query
result.  It won't teach you much about what the server is doing.

			regards, tom lane





view thread (3+ messages)  latest in thread

Message-ID: <657077.1703172763@sss.pgh.pa.us>
Permalink:  ../657077.1703172763@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/657077.1703172763@sss.pgh.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pensnarik@gmail.com
  Subject: Re: PostgreSQL 15.5 stops processing user queries
  In-Reply-To: <657077.1703172763@sss.pgh.pa.us>
  References: <CAN=gQ4A9Bq9=jri7qt8PUt4x7n576nZ6fqSpVx2DsdC=64uHeA@mail.gmail.com> <657077.1703172763@sss.pgh.pa.us>

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

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