X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 15ACFD1B4E5; Sun, 5 Oct 2003 04:21:28 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 62781-05; Sun, 5 Oct 2003 01:20:41 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 3D7F9D1B4EC; Sun, 5 Oct 2003 01:20:40 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h954KWT12351; Sun, 5 Oct 2003 00:20:32 -0400 (EDT) From: Bruce Momjian Message-Id: <200310050420.h954KWT12351@candle.pha.pa.us> Subject: Re: COUNT(*) again (was Re: [HACKERS] Index/Function organized In-Reply-To: <22013.1065302124@sss.pgh.pa.us> To: Tom Lane Date: Sun, 5 Oct 2003 00:20:32 -0400 (EDT) Cc: Hannu Krosing , Christopher Browne , pgsql-performance@postgresql.org, "pgsql-hackers@postgresql.org" X-Mailer: ELM [version 2.4ME+ PL106 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/150 X-Sequence-Number: 3898 Tom Lane wrote: > Hannu Krosing writes: > > The point I was trying to make was that faster count(*)'s is just a side > > effect. If we could (conditionally) keep visibility info in indexes, > > I think that's not happening, conditionally or otherwise. The atomicity > problems alone are sufficient reason why not, even before you look at > the performance issues. What are the atomicity problems of adding a create/expire xid to the index tuples? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073