Re: ksqo?

From: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ksqo?
Date: 2002-05-24 01:10:46
Message-ID: 20020523211046.7c039f48.nconway@klamath.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 22 May 2002 18:03:07 -0400
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> writes:
> > The current KSQO code is currently #ifdef'ed out, and the 'ksqo' GUC
> > variable does nothing. Is there a reason for keeping this code around?
> > (or conversely, what was the original justification for disabling it?)
>
> I disabled it because I didn't have time to fix it properly when it got
> broken by the 7.1 rewrite of UNION/INTERSECT/EXCEPT. I've been waiting
> to see whether anyone notices that it's gone ;-). So far the demand for
> it has been invisible, so it hasn't gotten fixed. On the other hand
> I'm not quite convinced that it never will get fixed, so I haven't
> applied the coup de grace.

Hmmm... Well, I'll take a look at it, but I'll probably just leave it
be -- since the optimization might actually return invalid results, it
doesn't seem like a very valuable thing to have, IMHO.

Cheers,

Neil

--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-05-24 04:31:00 Re: ksqo?
Previous Message Marc G. Fournier 2002-05-24 00:12:26 Re: Redhat 7.3 time manipulation bug