Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdOXk-0003oc-Ei for pgsql-bugs@arkaria.postgresql.org; Thu, 24 Apr 2014 18:38:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WdOXj-0000VA-NP for pgsql-bugs@arkaria.postgresql.org; Thu, 24 Apr 2014 18:38:43 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdOXh-0000V1-Mh for pgsql-bugs@postgresql.org; Thu, 24 Apr 2014 18:38:41 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdOXf-00016c-He for pgsql-bugs@postgresql.org; Thu, 24 Apr 2014 18:38:41 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s3OIccBI015616; Thu, 24 Apr 2014 14:38:38 -0400 From: Tom Lane To: maxim.boguk@gmail.com cc: pgsql-bugs@postgresql.org Subject: Re: BUG #10123: Weird entries in pg_stat_activity In-reply-to: <20140424101827.2714.39486@wrigleys.postgresql.org> References: <20140424101827.2714.39486@wrigleys.postgresql.org> Comments: In-reply-to maxim.boguk@gmail.com message dated "Thu, 24 Apr 2014 10:18:27 -0000" Date: Thu, 24 Apr 2014 14:38:38 -0400 Message-ID: <15615.1398364718@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org maxim.boguk@gmail.com writes: > During debug of the weird nagios database alerts about long transactions I > found that sometime pg_stat_activity contains very weird entries with > xact_start NOT NULL and state='idle'... > ... > What's more: i tested that problem on another databases - and found they > have same effect (so it doesn't look like a problem local to that single > exact database). So can you provide a self-contained test case for this? I tried to reproduce it here without much success, and I don't see a code path other than PREPARE TRANSACTION that could lead to this. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs