Re: [PERFORM] COUNT(*) again (was Re: Index/Function organized

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: [PERFORM] COUNT(*) again (was Re: Index/Function organized
Дата
Msg-id 200310051336.h95Daee20397@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: [PERFORM] COUNT(*) again (was Re: Index/Function organized table layout)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane wrote:
> 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.

But we don't update the tuple status for a commit, we just mark the xid
as committed.  We do have lazy status bits that prevent later lookups in
pg_clog, but we have those in the index already also.

What am I missing?

--
  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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Open 7.4 items
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Thoughts on maintaining 7.3