Re: queryId constant squashing does not support prepared statements
| От | Dmitry Dolgov |
|---|---|
| Тема | Re: queryId constant squashing does not support prepared statements |
| Дата | |
| Msg-id | cd4ouhwxlxb3yrq2l6cdhlckhu6qhens4unfakvruht2f56rn6@ey24svyxxo4k обсуждение исходный текст |
| Ответ на | Re: queryId constant squashing does not support prepared statements (Sami Imseih <samimseih@gmail.com>) |
| Ответы |
Re: queryId constant squashing does not support prepared statements
|
| Список | pgsql-hackers |
> On Fri, May 09, 2025 at 12:47:19PM GMT, Sami Imseih wrote: > So, I think we can create a new parse node ( parsenode.h ) that will only be > used in parsing (and gram.c only ) to track the start/end locations > and List and > based on this node we can create A_ArrayExpr and A_Expr with the List > of boundaries, > and then all we have to do is update ArrayExpr with the boundaries during > the respective transformXExpr call. This seems like a much simpler approach > that also addresses Michael's concern of defining static variables in gram.y to > track the boundaries. The static variables was only part of the concern, another part was using A_Expr to carry this information, which will have impact on lots of unrelated code.
В списке pgsql-hackers по дате отправления: