Re: Query Jumbling for CALL and SET utility statements
От | Julien Rouhaud |
---|---|
Тема | Re: Query Jumbling for CALL and SET utility statements |
Дата | |
Msg-id | 20221010131647.dflnfd4rhqilldoj@jrouhaud обсуждение исходный текст |
Ответ на | Re: Query Jumbling for CALL and SET utility statements ("Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>) |
Ответы |
Re: Query Jumbling for CALL and SET utility statements
|
Список | pgsql-hackers |
Hi, On Mon, Oct 10, 2022 at 03:04:57PM +0200, Drouvot, Bertrand wrote: > > On 10/7/22 6:13 AM, Michael Paquier wrote: > > > > Probably. One part that may be tricky though is the location of the > > constants we'd like to make generic, but perhaps this could be handled > > by using a dedicated variable type that just maps to int? > > It looks to me that we'd also need to teach the perl parser which fields per > statements struct need to be jumbled (or more probably which ones to exclude > from the jumbling, for example funccall in CallStmt). Not sure yet how to > teach the perl parser, but I'll build this list first to help decide for a > right approach, unless you already have some thoughts about it? Unless I'm missing something both can be handled using pg_node_attr() annotations that already exists?
В списке pgsql-hackers по дате отправления: