Re: Overriding the optimizer
От | Jaime Casanova |
---|---|
Тема | Re: Overriding the optimizer |
Дата | |
Msg-id | c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Overriding the optimizer ("Jim C. Nasby" <jnasby@pervasive.com>) |
Ответы |
Re: Overriding the optimizer
|
Список | pgsql-performance |
> > Yeah it would - an implementation I have seen that I like is where the > > developer can supply the *entire* execution plan with a query. This is > > complex enough to make casual use unlikely :-), but provides the ability > > to try out other plans, and also fix that vital query that must run > > today..... > > Being able to specify an exact plan would also provide for query plan > stability; something that is critically important in certain > applications. If you have to meet a specific response time requirement > for a query, you can't afford to have the optimizer suddenly decide that > some other plan might be faster when in fact it's much slower. Plan stability doesn't mean time response stability... The plan that today is almost instantaneous tomorrow can take hours... -- regards, Jaime Casanova (DBA: DataBase Aniquilator ;)
В списке pgsql-performance по дате отправления: