WinterUnicorn

Invalid plpgsql_recurse_level after catch any exception

2

Hi. We have an issues related to the invalid value of plpgsql_recurse_level counter in the PG13 and current master branch (Postgres 14). The issue is that when we catch and...

Ignore hints in prepared statements with array arguments

4

Case to reproduce: We have an issues with prepared statements that use arrays in arguments. In this case pg_hint_plan don't pass preceding sql check. Is it possible to adds '[',...

We have several cases where we need hints to be anywhere inside query and at the same time we need analysis to understand that hints are not part of string...

We have an issues related to the invalid value of plpgsql_recurse_level counter in the PG13 and current master branch (Postgres 14). The issue appears when we catch and handle any...

We have hints that are used by another extension or hints that are used by an external applications(outside of the database layer). We also have cases when some queries using...

We have an issues with prepared statements that use arrays as arguments. In this case pg_hint_plan don't pass preceding sql check. Example: ``` prepare test_query(numeric[]) as /*+ MergeJoin(t1 t2) */...

We have an issues with segfault on pg_hint_plan for PG13. We don't have stable case to reproduce theses issues (issue is floating) but it is critical for us because database...

Pull request for synchronization with actual postgresql core code of set_rel_pathlist and dependent functions.