Re: automatically generating node support functions
Andres Freund <andres@anarazel.de>
Hi, On 2022-07-11 15:54:22 -0400, Tom Lane wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > On Mon, Jul 11, 2022 at 1:57 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> More generally, I'm having second thoughts about the wisdom of > >> auto-generating the NodeTag enum at all. With the current setup, > >> I am absolutely petrified about the risk of silent ABI breakage > >> thanks to the enum order changing. > > > I think this is a valid concern, but having it be automatically > > generated is awfully handy, so I think it would be nice to find some > > way of preserving that. > > Agreed. The fundamental problem seems to be that each build toolchain > has its own source of truth about the file processing order, but we now > see that there had better be only one. We could make the sole source > of truth about that be gen_node_support.pl itself, I think. > > We can't simply move the file list into gen_node_support.pl, because > (a) the build system has to know about the dependencies involved Meson has builtin support for tools like gen_node_support.pl reporting which files they've read and then to use those as dependencies. It'd not be a lot of effort to open-code that with make either. Doesn't look like we have dependency handling in Solution.pm? > (b) gen_node_support.pl wouldn't know what to do in VPATH situations. We could easily add a --include-path argument or such. That'd be trivial to set for all of the build solutions. FWIW, for meson I already needed to add an option to specify the location of output files (since scripts are called from the root of the build directory). Greetings, Andres Freund
Commits
-
Fix MSVC build script's check for obsolete node support functions.
- 9a9f25e21742 16.0 landed
-
Improve performance of ORDER BY / DISTINCT aggregates
- 1349d2790bf4 16.0 cited
-
doc: Fix typos in protocol.sgml
- a69959fab2f3 16.0 cited
-
Tighten up parsing logic in gen_node_support.pl.
- 7c0eb3c622eb 16.0 landed
-
Add defenses against unexpected changes in the NodeTag enum list.
- eea9fa9b250f 16.0 landed
-
Add copy/equal support for XID lists
- 5ca0fe5c8ad7 16.0 landed
-
Rationalize order of input files for gen_node_support.pl.
- bf022d337ef0 16.0 landed
-
Make assorted quality-of-life improvements in gen_node_support.pl.
- 8eccaf652542 16.0 landed
-
Doc: rearrange high-level commentary about node support coverage.
- 3cd0ac987819 16.0 landed
-
Automatically generate node support functions
- 964d01ae90c3 16.0 landed
-
Adjust node serialization tag of A_Expr for consistency
- bf1f4a364d6c 16.0 landed
-
Remove T_Join and T_Plan
- 251154bebe98 16.0 landed
-
Reformat some more node comments
- 3140f089855c 16.0 landed
-
Reformat some node comments
- 835d476fd21b 16.0 landed
-
Remove JsonPathSpec typedef
- dc2be6ed47e5 15.0 landed
-
Add missing enum tag in enum used in nodes
- d47a11da9e5c 15.0 landed
-
Add Cardinality typedef
- 6fe0eb963d38 15.0 landed
-
Make node output prefix match node structure name
- e58136069687 15.0 landed
-
Add WRITE_INDEX_ARRAY
- bdeb2c4ec270 15.0 landed
-
Add COPY_ARRAY_FIELD and COMPARE_ARRAY_FIELD
- 308da179e7c2 15.0 landed
-
Remove T_Expr
- 853992919773 15.0 landed
-
Change NestPath node to contain JoinPath node
- 18fea737b5e4 15.0 landed
-
Change SeqScan node to contain Scan node
- 2226b4189bb4 15.0 landed
-
Check the size in COPY_POINTER_FIELD
- c1132aae336c 15.0 landed
-
Remove T_MemoryContext
- 256909c6c167 15.0 landed
-
Add missing enum tags in enums used in nodes
- 983bdc4fac49 15.0 landed
-
Rename some node support functions for consistency
- 31360381f0a5 15.0 landed
-
Rename argument of _outValue()
- 3d25b4ea6e2c 15.0 landed
-
Rename NodeTag of ExprState
- d9a38c52cef3 15.0 landed