| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com> |
| Subject: | Re: Damage control for planner's get_actual_variable_endpoint() runaway |
| Date: | 2022-11-21 12:22:13 |
| Message-ID: | 20221121122213.egy3bxhyul67y3iv@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Nov-21, Jakub Wartak wrote:
> b) I was wondering about creating a new wait class "Planner" with the
> event "ReadingMinMaxIndex" (or similar). The obvious drawback is the
> naming/categorization as wait events are ... well.. as the name "WAIT"
> implies, while those btree lookups could easily be ON-CPU activity.
I think we should definitely do this, regardless of any other fixes we
add, so that this condition can be identified more easily. I wonder if
we can backpatch it safely.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Always assume the user will do much worse than the stupidest thing
you can imagine." (Julien PUYDT)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2022-11-21 12:30:47 | Re: Catalog_xmin is not advanced when a logical slot is lost |
| Previous Message | Alvaro Herrera | 2022-11-21 12:09:08 | Re: Catalog_xmin is not advanced when a logical slot is lost |