aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-04-11 13:18:50 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-04-11 13:18:54 -0400
commitcee83ef4a243c87683a4f472bab0e005b8b56f3c (patch)
treede688109bb020fdb9a15cf6382e4d5107af79d38 /src/backend/executor/nodeModifyTable.c
parent92899992e13a089fb8915b02e45792998996530e (diff)
downloadpostgresql-cee83ef4a243c87683a4f472bab0e005b8b56f3c.tar.gz
postgresql-cee83ef4a243c87683a4f472bab0e005b8b56f3c.zip
Invoke submake-generated-headers during "make check", too.
The MAKELEVEL hack to prevent submake-generated-headers from doing anything in child make runs means that we have to explicitly invoke it at top level for "make check", too, in case somebody proceeds directly to that without an explicit "make all". (I think this usage had parallel-make hazards even before the addition of more generated headers; but it was totally broken as of 3b8f6e75f.) Out of paranoia, force the submake-libpq target to depend on submake-generated-headers, too. This seems to not be absolutely necessary today, but it's not really saving us anything to omit the ordering dependency, and it'll likely break someday without it. Discussion: https://postgr.es/m/20180411103930.GB31461@momjian.us
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions