Re: pg_checksums: Reorder headers in alphabetical order
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Michael Banck <mbanck@gmx.net>,
pgsql-hackers@postgresql.org
Date: 2024-09-21T03:09:17Z
Lists: pgsql-hackers
Fujii Masao <masao.fujii@oss.nttdata.com> writes: > I don’t have any objections to this commit, but I’d like to confirm > whether we really want to proactively reorder #include directives, > even for standard C library headers. I'm hesitant to do that. We can afford to insist that our own header files be inclusion-order-independent, because we have the ability to fix any problems that might arise. We have no ability to do something about it if the system headers on $random_platform have inclusion order dependencies. (In fact, I'm fairly sure there are already places in plperl and plpython where we know we have to be careful about inclusion order around those languages' headers.) So I would tread pretty carefully around making changes of this type, especially in long-established code. I have no reason to think that the committed patch will cause any problems, but I do think it's mostly asking for trouble. regards, tom lane
Commits
-
Alphabetize #include directives in pg_checksums.c.
- afb03e2ebf59 18.0 landed
-
Add progress reporting to pg_checksums
- 280e5f14056b 12.0 cited