Re: Query Jumbling for CALL and SET utility statements - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Query Jumbling for CALL and SET utility statements
Date
Msg-id 20221010131647.dflnfd4rhqilldoj@jrouhaud
Whole thread Raw
In response to Re: Query Jumbling for CALL and SET utility statements  ("Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>)
Responses Re: Query Jumbling for CALL and SET utility statements  (Michael Paquier <michael@paquier.xyz>)
List 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 by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Query Jumbling for CALL and SET utility statements
Next
From: Ian Lawrence Barwick
Date:
Subject: doc: add entry for pg_get_partkeydef()