agora inbox for pgsql-sql@postgresql.org  

help / color / mirror / Atom feed

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?
Date: Fri, 21 Jul 2017 13:23:30 -0400
Message-ID: <17755.1500657810@sss.pgh.pa.us> (raw)
In-Reply-To: <e00cc4cd-05d1-7fd1-a7a0-e7fea6e81919@gmail.com>
References: <5e59f5e0-7168-fb80-d038-7fe9adad4aa9@gmail.com>
	<29711.1500646472@sss.pgh.pa.us>
	<e00cc4cd-05d1-7fd1-a7a0-e7fea6e81919@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>

Tim Dudgeon <tdudgeon.ml@gmail.com> writes:
> Yes, the state is "idle", and the command is "COMMIT".
> But if the COMMIT has completed then the process should finish and the 
> row not be present?

Well, that's up to the connected client whether it's going to terminate
the session or not.

> So is what you are suggesting that in my case I'm using a connection 
> pool, and the COMMIT has completed successfully, the connection released 
> back to the pool, but not yet closed, so that process is still running?

That's sort of the point of a connection pooler, to re-use database
sessions rather than establishing new ones all the time.  But the
database doesn't know that a pooler is in use; it just sees a client
connection that's not doing anything right now.

			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

view thread (4+ messages)

Message-ID: <17755.1500657810@sss.pgh.pa.us>
Permalink:  ../17755.1500657810@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17755.1500657810@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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tdudgeon.ml@gmail.com
  Subject: Re: commit not completing - how to investigate?
  In-Reply-To: <17755.1500657810@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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox