Re: Ordering of header file inclusion
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-10-20T17:31:00Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Make the order of the header file includes consistent.
- e0487223ecac 13.0 landed
-
Make the order of the header file includes consistent in backend modules.
- 14aec0350230 13.0 landed
-
Make the order of the header file includes consistent in non-backend modules.
- dddf4cdc3300 13.0 landed
-
Make the order of the header file includes consistent in contrib modules.
- 7e735035f208 13.0 landed
On Sun, Oct 20, 2019 at 1:20 AM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > > diff --git a/contrib/bloom/blcost.c b/contrib/bloom/blcost.c > index f9fe57f..6224735 100644 > --- a/contrib/bloom/blcost.c > +++ b/contrib/bloom/blcost.c > @@ -12,10 +12,10 @@ > */ > #include "postgres.h" > > +#include "bloom.h" > #include "fmgr.h" > #include "utils/selfuncs.h" > > -#include "bloom.h" > > /* > * Estimate cost of bloom index scan. > > This class of change I don't like. > > The existing arrangement keeps "other" header files separate from the > header file of the module itself. It seems useful to keep that separate. > Thanks Peter for your thoughts, I have modified the changes based on your suggestions. I have included the module header file in the beginning. The changes are attached in the previous mail. Please let me know your suggestions for any changes. Regards, Vignesh EnterpriseDB: http://www.enterprisedb.com