Re: Symbolic names for the values of typalign and typstorage - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Symbolic names for the values of typalign and typstorage
Date
Msg-id 5063.1583205724@sss.pgh.pa.us
Whole thread Raw
In response to Re: Symbolic names for the values of typalign and typstorage  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Symbolic names for the values of typalign and typstorage
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2020-Mar-02, Tom Lane wrote:
>> One thing that I'm not totally happy about, as this stands, is that
>> we have to #include "catalog/pg_type.h" in various places we did
>> not need to before (although only a fraction of the files I touched
>> need that).

> If we think that pg_type.h is the header to handle access to the pg_type
> catalog, then I would think that the function declarations at the bottom
> should be in some "internal" header file; then we can get rid of most
> the #includes in pg_type.h.

Well, aside from indirect inclusions, pg_type.h also brings in a bunch
of type OID macros, which I feel we don't want to broadcast everywhere.

One argument in favor of sticking these new macros somewhere "more
central" is that they apply to both pg_type and pg_attribute (that
is, attalign and attstorage also use them).  That's not a strong
argument, maybe, but it's something.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Fastpath while arranging the changes in LSN order in logical decoding
Next
From: Chris Bandy
Date:
Subject: Re: [PATCH] Documentation bug related to client authentication usingTLS certificate