Re: Ordering of header file inclusion

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Ordering of header file inclusion
Date: 2019-11-12 01:03:40
Message-ID: CALDaNm00XEr6g1UzGtzFWdp65xbkgQLdJrkaJQ9gytB2=d69TA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 11, 2019 at 11:36 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Sun, Nov 10, 2019 at 5:30 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> >
> [review_latest_patch]:
>
> Do we want to consider the ordering of map file inclusions as well
> (see the changes pointed out below)? If so, what all we should
> validate, is compilation of these modules sufficient? Tom, anyone, do
> you have any opinion on this?
>

Even I don't know how to validate the above changes by some test
application, other than by compiling.

> 1.
> utf8_and_cyrillic.c
>
> #include "fmgr.h"
> #include "mb/pg_wchar.h"
> -#include "../../Unicode/utf8_to_koi8r.map"
> #include "../../Unicode/koi8r_to_utf8.map"
> -#include "../../Unicode/utf8_to_koi8u.map"
> #include "../../Unicode/koi8u_to_utf8.map"
> +#include "../../Unicode/utf8_to_koi8r.map"
> +#include "../../Unicode/utf8_to_koi8u.map"
>
> PG_MODULE_MAGIC;
>
> 2.
> utf8_and_iso8859.c
> ..
> #include "../../Unicode/iso8859_13_to_utf8.map"
> #include "../../Unicode/iso8859_14_to_utf8.map"
> #include "../../Unicode/iso8859_15_to_utf8.map"
> +#include "../../Unicode/iso8859_16_to_utf8.map"
> #include "../../Unicode/iso8859_2_to_utf8.map"
> #include "../../Unicode/iso8859_3_to_utf8.map"
> #include "../../Unicode/iso8859_4_to_utf8.map"
> @@ -39,7 +41,6 @@
> #include "../../Unicode/utf8_to_iso8859_7.map"
> #include "../../Unicode/utf8_to_iso8859_8.map"
> #include "../../Unicode/utf8_to_iso8859_9.map"
> -#include "../../Unicode/iso8859_16_to_utf8.map"
>

Thanks Amit for your comments. Please find the updated patch which
does not include the changes mentioned above. I will post a separate
patch for these changes based on the response from others.

Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com

Attachment Content-Type Size
0001-Make-the-order-of-the-header-file-includes-consistent-backend-nov12th.patch text/x-patch 119.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-11-12 01:11:53 Re: adding partitioned tables to publications
Previous Message Michael Paquier 2019-11-12 00:35:03 Re: [PATCH][DOC] Fix for PREPARE TRANSACTION doc and postgres_fdw message.