| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: KSQO parameter |
| Date: | 2001-08-10 18:02:22 |
| Message-ID: | 18634.997466542@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Is there any value to KQSO parameter? It was for complex OR clauses. I
> thought Tom fixed most of that.
The last set of tests that I did (~7.0) showed that it was still
marginally faster than the default approach. Not a "must have"
like it used to be for those queries, though.
As of 7.1 it is disabled anyway, because I didn't have time to update
the KSQO code for the new implementation of UNION and friends.
We should either update the code or remove it entirely. I still don't
have the time or interest to do #1, but I'm not quite ready to do #2
either ... does anyone out there want to work on it?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-10 20:08:50 | JDBC pg_description update needed for CVS tip |
| Previous Message | Bruce Momjian | 2001-08-10 17:19:14 | KSQO parameter |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miguel Gonzalez | 2001-08-11 16:10:02 | Creating users |
| Previous Message | Bruce Momjian | 2001-08-10 17:19:14 | KSQO parameter |