Re: Buglist

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Vivek Khera <khera(at)kcilink(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Buglist
Date: 2003-08-20 20:10:31
Message-ID: 3F43D5B7.2000108@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Tom Lane wrote:

> Recall also that "committed deleted" does not mean "safe to remove".
> There may still be live transactions that could see the tuple. The
> "committed deleted" bit just exists to allow subsequent visitors to the
> row to skip one of the more expensive steps in deciding whether they can
> see it or not.
>
> To determine that a row is removable requires additional tests above and
> beyond what backends normally do.

Aah - there is the first bullet hole in my multi-ctid-index-idea. Now
the question becomes how expensive these tests are (if a normal backend
can do them at all within reason)?

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-08-20 20:26:29 Re: 7.4b1 vs 7.3.4 performance
Previous Message Tom Lane 2003-08-20 20:02:06 Re: Buglist

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-08-20 20:41:32 Re: "SELECT IN" Still Broken in 7.4b
Previous Message Tom Lane 2003-08-20 20:02:06 Re: Buglist