X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9A0F3D1B518 for ; Fri, 14 Nov 2003 18:51:45 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 42993-08 for ; Fri, 14 Nov 2003 14:51:15 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id A991AD1B502 for ; Fri, 14 Nov 2003 14:51:13 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hAEInx19003132; Fri, 14 Nov 2003 13:49:59 -0500 (EST) To: Hannu Krosing Cc: Christopher Browne , pgsql-performance@postgresql.org Subject: Re: Help with count(*) In-reply-to: <1068831807.2540.44.camel@fuji.krosing.net> References: <200311141251.38786.mallah@trade-india.com> <1068831807.2540.44.camel@fuji.krosing.net> Comments: In-reply-to Hannu Krosing message dated "Fri, 14 Nov 2003 19:43:27 +0200" Date: Fri, 14 Nov 2003 13:49:59 -0500 Message-ID: <3131.1068835799@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/116 X-Sequence-Number: 4676 Hannu Krosing writes: > Christopher Browne kirjutas R, 14.11.2003 kell 16:13: >> I have seen this happen somewhat-invisibly when a JDBC connection >> manager opens transactions for each connection, and then no processing >> happens to use those connections for a long time. The open >> transactions prevent vacuums from doing any good... > Can't the backend be made to delay the "real" start of transaction until > the first query gets executed ? That is on the TODO list. I looked at it briefly towards the end of the 7.4 development cycle, and decided that it was nontrivial and I didn't have time to make it happen before beta started. I don't recall why it didn't seem trivial. regards, tom lane