Re: ignore_killed_tuples is always true

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Casanova <systemguards(at)gmail(dot)com>
Cc: ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org
Subject: Re: ignore_killed_tuples is always true
Date: 2006-02-11 15:52:50
Message-ID: 8012.1139673170@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Jaime Casanova <systemguards(at)gmail(dot)com> writes:
> On 2/10/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What is the point of removing it? You cannot argue that saving
>> one if-test per tuple is a worthwhile speedup.

> to clean code?

It's not saving any noticeable amount of code, and what it is doing
is removing functionality we might want someday. It's not hard to
imagine pgstattuple or VACUUM or other maintenance operations wanting
to look at killed index entries.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-02-11 16:59:05 Re: Skipping VACUUM of indexes when no work required
Previous Message Jaime Casanova 2006-02-11 05:31:11 Re: ignore_killed_tuples is always true