From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Dudgeon <tdudgeon.ml@gmail.com>
cc: pgsql-sql@postgresql.org
Subject: Re: commit not completing - how to investigate?
In-reply-to: <5e59f5e0-7168-fb80-d038-7fe9adad4aa9@gmail.com>
References: <5e59f5e0-7168-fb80-d038-7fe9adad4aa9@gmail.com>
Comments: In-reply-to Tim Dudgeon <tdudgeon.ml@gmail.com>
	message dated "Fri, 21 Jul 2017 12:32:57 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <29710.1500646472.1@sss.pgh.pa.us>
Date: Fri, 21 Jul 2017 10:14:32 -0400
Message-ID: <29711.1500646472@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Tim Dudgeon <tdudgeon.ml@gmail.com> writes:
> I have a situation where the pg_stat_activity view shows that can have 
> some processes that are idle and not completing. In some cases the 
> statement being executed is COMMIT.

Are you sure you're interpreting the view properly?  If the session
state is shown as idle, it's idle.  We used to show the query field
as empty in that case, but recent PG versions allow the query field
to continue to show the last-completed command.

			regards, tom lane


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql