| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ksqo? |
| Date: | 2002-05-22 22:03:07 |
| Message-ID: | 393.1022104987@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-05-22 22:18:58 | Me in California |
| Previous Message | Tom Lane | 2002-05-22 21:56:21 | Re: Killing dead index tuples before they get vacuumed |