You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue would be able to crash the server when for example setting
pg_hint_plan.parse_messages to 'error' in a session and trigger an error
via a hint that cannot be parsed.
Per issue #162. This issue does not exist in 14 and newer branches
because get_current_hint_string() is much more careful with the handling
of pfree()'d current_hint_str there.
Reported-by: Pogosyan Vardan
Author: Sergei Glukhov
Backpatch-through: 12
This issue would be able to crash the server when for example setting
pg_hint_plan.parse_messages to 'error' in a session and trigger an error
via a hint that cannot be parsed.
Per issue #162. This issue does not exist in 14 and newer branches
because get_current_hint_string() is much more careful with the handling
of pfree()'d current_hint_str there.
Reported-by: Pogosyan Vardan
Author: Sergei Glukhov
Backpatch-through: 12
Thanks for the report. I have applied a fix on PG12 and PG13 where the problem appears. In PG14 this code is much more careful. PG11 is not supported anymore, unfortunately.
Hello!
The following commands calls SIGABRT:
This happens on the PG11-PG13 branches.
Here is the backtrace:
Suggested fix by svglukhov is in the attachment.
fix-invalid-hint-declarations.txt
The text was updated successfully, but these errors were encountered: