From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Hannu Krosing <hannu@tm.ee>
Cc: Christopher Browne <cbbrowne@libertyrms.info>
Cc: pgsql-performance@postgresql.org, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: COUNT(*) again (was Re: [HACKERS] Index/Function organized table layout)
Date: Sun, 05 Oct 2003 02:08:31 -0400
Message-ID: <28313.1065334111@sss.pgh.pa.us> (raw)
In-Reply-To: <200310050420.h954KWT12351@candle.pha.pa.us>
References: <200310050420.h954KWT12351@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> 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?
You can't update a tuple's status in just one place ... you have to
update the copies in the indexes too.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, hannu@tm.ee, cbbrowne@libertyrms.info, pgsql-hackers@postgresql.org
Subject: Re: COUNT(*) again (was Re: [HACKERS] Index/Function organized table layout)
In-Reply-To: <28313.1065334111@sss.pgh.pa.us>
References: <200310050420.h954KWT12351@candle.pha.pa.us> <28313.1065334111@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox