Re: automatically generating node support functions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: automatically generating node support functions
Date
Msg-id 101171fc-da4c-7799-991d-65ad84f53d7d@enterprisedb.com
Whole thread Raw
In response to Re: automatically generating node support functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: automatically generating node support functions
Re: automatically generating node support functions
List pgsql-hackers
On 11.07.22 19:57, Tom Lane wrote:
> So at this point I'm rather attracted to the idea of reverting to
> a manually-maintained NodeTag enum.  We know how to avoid ABI
> breakage with that, and it's not exactly the most painful part
> of adding a new node type.

One of the nicer features is that you now get to see the numbers 
assigned to the enum tags, like

     T_LockingClause = 91,
     T_XmlSerialize = 92,
     T_PartitionElem = 93,

so that when you get an error like "unsupported node type: %d", you can 
just look up what it is.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Making CallContext and InlineCodeBlock less special-case-y
Next
From: Juan José Santamaría Flecha
Date:
Subject: Re: WIN32 pg_import_system_collations