Re: [RFC] building postgres with meson

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: [RFC] building postgres with meson
Date: 2022-08-09 07:10:55
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


I was looking at re-unifying that the meson patchset had introduced
for temporary ease during hacking with Testing that I noticed that
either I and my machine is very confused, or's check whether it can
skip work is bogus.

I noticed that, despite having code to avoid rerunning when the input files
are older than the .def file, it always runs.

# if the def file exists and is newer than all input object files, skip
# its creation
if (-f $deffile
&& (-M $deffile > max(map { -M } <$ARGV[0]/*.obj>)))
print "Not re-generating $defname.DEF, file already exists.\n";

My understanding of -M is that it returns the time delta between the file
modification and the start of the script. Which makes the use of max() bogus,
since it'll return the oldest time any input has been modified, not the
newest. And the condition needs to be inverted, because we want to skip the
work if $deffile is *newer*, right?

Am I missing something here?

I'm tempted to just remove the not-regenerating logic - shouldn't
run if there's nothing to do, and it'll e.g. not notice if there's an
additional input that wasn't there during the last invocation of


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-08-09 07:12:36 Re: An attempt to avoid locally-committed-but-not-replicated-to-standby-transactions in synchronous replication
Previous Message David Rowley 2022-08-09 07:10:00 Re: [PoC] Reducing planning time when tables have many partitions