| From: | Jim Finnerty <jfinnert(at)amazon(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: On disable_cost |
| Date: | 2019-11-01 16:30:52 |
| Message-ID: | 1572625852934-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
re: coping with adding disable_cost more than once
Another option would be to have a 2-part Cost structure. If disable_cost is
ever added to the Cost, then you set a flag recording this. If any plans
exist that have no disable_costs added to them, then the planner chooses the
minimum cost among those, otherwise you choose the minimum cost path.
-----
Jim Finnerty, AWS, Amazon Aurora PostgreSQL
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-11-01 16:43:14 | Re: On disable_cost |
| Previous Message | Robert Haas | 2019-11-01 16:30:49 | Re: [PATCH] Implement INSERT SET syntax |