| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | 李奇隆 <12232409(at)mail(dot)sustech(dot)edu(dot)cn> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PG does not support one function of its extension pg_hint_plan |
| Date: | 2024-11-01 13:16:09 |
| Message-ID: | ZyTUmVBN_Q-QOQg6@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)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?"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-11-01 13:37:56 | Re: Inquiry on Future Plans for Enhancements to PostgreSQL MVCC Model and Vacuum Process |
| Previous Message | Andreas Karlsson | 2024-11-01 13:08:07 | Re: Collation & ctype method table, and extension hooks |