Re: automatically generating node support functions

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automatically generating node support functions
Date: 2022-07-11 20:26:46
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2022-07-11 16:17:28 -0400, Robert Haas wrote:
> On Mon, Jul 11, 2022 at 3:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > We can't simply move the file list into, because
> > (a) the build system has to know about the dependencies involved, and
> > (b) wouldn't know what to do in VPATH situations.
> > However, we could have contain a canonical list
> > of the files it expects to be handed, and make it bitch if its
> > arguments don't match that.
> Sorry if I'm being dense, but why do we have to duplicate the list of
> files instead of having just sort whatever list
> the build system provides to it?

Because right now there's two buildsystems already (look at Looks like we'll briefly have three, then two again.


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-11 20:36:02 Re: automatically generating node support functions
Previous Message Andres Freund 2022-07-11 20:25:33 Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work