Re: ignore_killed_tuples is always true

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 05:31:11
Message-ID: c2d9e70e0602102131y5566939cwfaf8e954aba9457a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On 2/10/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp> writes:
> > I found IndexScanDesc->ignore_killed_tuples is always true.
> > Is this still needed?
>
> What is the point of removing it? You cannot argue that saving
> one if-test per tuple is a worthwhile speedup.
>
> regards, tom lane
>

to clean code?

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-02-11 15:52:50 Re: ignore_killed_tuples is always true
Previous Message Bruce Momjian 2006-02-11 03:32:57 Re: contrib/xinetops for 8.1 "patch"