| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael McCarthy <michael(at)tcsi(dot)com> |
| Cc: | David C Hartwig Jr <daybee(at)bellatlantic(dot)net>, pgsql-sql(at)postgreSQL(dot)org, Hemant Yevale <hemant(at)tcsi(dot)com>, Savyasachi Jog <jog(at)tcsi(dot)com> |
| Subject: | Re: [SQL] problem with OR'ed AND queriess |
| Date: | 1999-12-22 04:13:52 |
| Message-ID: | 14561.945836032@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Michael McCarthy <michael(at)tcsi(dot)com> writes:
> A quick examination of backend/optimizer/prep/prepkeyset.c shows me that
> there is some qualification of a query for keyset optimization; is there
> any reason why I should not always set ksqo on?
If it seems to win more often than not for your query mix, go for it.
ksqo is a hack that I'm hoping to eliminate in the next release or
three. But right now, it's a mighty useful hack if you do a lot of
OR-of-AND queries...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bron Till | 1999-12-23 03:22:41 | |
| Previous Message | Bruce Momjian | 1999-12-22 03:51:51 | Re: [SQL] problem with OR'ed AND queriess |