Re: src/tools/pginclude considered harmful (was Re:

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, Kris Jurka <books(at)ejurka(dot)com>
Subject: Re: src/tools/pginclude considered harmful (was Re:
Date: 2006-07-17 22:46:51
Message-ID: 8997.1153176411@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> FYI, 527 include were removed from non-header C files in this run. That
> is not something that can be easily done manually.

It's not so easily done automatically, either :-(. I'm not sure why
this go-round was so much more painful than the last, but it very
clearly exposed the deficiencies in your testing process. Mainly,
that you tested only one set of configure options on one platform.

I would say that minimum requirements for doing this again in future
are (1) test with and without --enable-cassert, and (2) test with and
without EXEC_BACKEND. We *know* that both those things change the
set of headers required. It might be necessary to actually test the
WIN32 port separately --- EXEC_BACKEND is close but not the same.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-07-17 23:06:53 Re: pg_regress in C
Previous Message Tom Lane 2006-07-17 22:41:26 Re: Proposed patch for contrib/cube

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-07-17 23:06:53 Re: pg_regress in C
Previous Message Tom Lane 2006-07-17 22:41:26 Re: Proposed patch for contrib/cube