2 ms·

I got your point. But if we can also use all the indexes, and other stuff, but without SQL and mainly without any dynamic lookup. (I dont need to parse SQL, No

I got your point. But if we can also use all the indexes, and other stuff, but without SQL and mainly without any dynamic lookup. (I dont need to parse SQL, No need to validate if it is correct or not, no need to dynamically find which table to load etc). Don't you think it will be even 1% of faster than SQL? (ofcourse I wont go that way for 1%)

justintocci 13y ago
That would then depend on your server. If nothing really changes your server could plan the first run and re-use that plan each time. I know I can do that with Postgres, your server may be different. To figure out what the actual percentage is postgres has the ability to tell you how long it takes to plan a query so I would say try that. I wouldn't hazard a guess since its going to depend on too many factors and its so easy to just find out from the planner.