"Adam Lang" <[EMAIL PROTECTED]> forwards:
>> In Postgres I am forced to create three indicies: one including all
>> three columns, one for col2 and col3, and one for just col3.
Depending on what his queries actually are, perhaps it's sufficient
to create one index on (col3,col2,col1), rather than
Title: RE: [GENERAL] Fw: [PHP] Fooling the query optimizer
Running this query:
"SELECT * WHERE col3 = x"
with a btree index on (col1, col2, col3) cannot be performed in an efficient manner, in any database, because you have specified the column order to be col1, col2, col3. I
On another list, someone posted this question. Are they correct, old
problem, etc.? I'll pass whatever info there is back to the originating
list.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
- Original Message -
From: "Brent R.Matzelle"
