Re: PG does not support one function of its extension pg_hint_plan
От | Bruce Momjian |
---|---|
Тема | Re: PG does not support one function of its extension pg_hint_plan |
Дата | |
Msg-id | ZyTUmVBN_Q-QOQg6@momjian.us обсуждение исходный текст |
Ответ на | PG does not support one function of its extension pg_hint_plan (李奇隆 <12232409@mail.sustech.edu.cn>) |
Ответы |
Re: PG does not support one function of its extension pg_hint_plan
|
Список | pgsql-hackers |
On Fri, Nov 1, 2024 at 11:13:09AM +0800, 李奇隆 wrote: > HI, all hackers: > > > In the GitHub repository for PostgreSQL’s pg_hint_plan extension, there is an > issue where the generated join order does not match the assigned join order. > After reviewing the source code, I found that this inconsistency with input > hints is due to PostgreSQL’s implementation and is not a bug in pg_hint_plan. Just to clarify, the bug is not in pg_hint_plan but in the fact that the Postgres server ignores "disable_cost of disabled operators in the initial phase of cost estimation," right? -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com When a patient asks the doctor, "Am I going to die?", he means "Am I going to die soon?"
В списке pgsql-hackers по дате отправления: