Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id D4A29633652 for ; Wed, 4 Nov 2009 17:52:10 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 46477-03 for ; Wed, 4 Nov 2009 21:51:55 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by mail.postgresql.org (Postfix) with ESMTP id 086C563343A for ; Wed, 4 Nov 2009 17:51:59 -0400 (AST) Received: by iwn16 with SMTP id 16so5092206iwn.29 for ; Wed, 04 Nov 2009 13:51:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=7cfKybdBOUgnE46m4bvtPifE4WIL8tWps7JfJd7J1vg=; b=MGGNVs0535M4gd9fSYO3ilDme7zT1U5+n8RDpVX18dNG9t5OSZex6NdzKnuwnOqh+f rB9cZ+4WQHaMBFD/A3W/da9pguN0Rsnw3Nk+g84Dz2KsXY9ADR2LQNtuBAglx2Ydr5bY L+hQRbEGv7mJG6xR4M6yjkhz3/K4TohwcvPEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ETYRCWL8RXmn4hc0InBRn7U85BqLOhC0kbaEoOffHJ5/dYw2HsafyNcA2l5vaTcDFa JM+kWrNlJYLn2MYQTw6TTJqRwAPgUSVwk+fAKsNu1k+FXtOkLaXw0S/mXZfjSMtdmtdP uTCY7XajGPFX7AW7ugU/oPt7KcQm841MbLIPQ= MIME-Version: 1.0 Received: by 10.231.125.28 with SMTP id w28mr890553ibr.50.1257371517113; Wed, 04 Nov 2009 13:51:57 -0800 (PST) In-Reply-To: References: Date: Wed, 4 Nov 2009 14:51:57 -0700 Message-ID: Subject: Re: vacuum'ing toast crumbs, detecting dangling transactions From: Scott Marlowe To: Dave Crooke Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.508 tagged_above=-10 required=5 tests=AWL=0.091, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200911/52 X-Sequence-Number: 36220 On Wed, Nov 4, 2009 at 2:18 PM, Dave Crooke wrote: > 2. If there is a hanging transaction, what's the best way to trace it from > the PG end? Client is classic Java (Spring / Hibernate / Apache DBCP) if > that matters. Last place I worked we had the same issue and it was in our jdbc settings or maybe needed an upgraded version. It was some slick trick someone thought of to do a commit;begin; at the end of each access to the db. It's that begin; that gets in the way, especially if there's an occasional select 1 to make sure the connection is alive.