Re: After upgrading libpq, the same function(PQftype) call returns a different OID - Mailing list pgsql-general

From Tom Lane
Subject Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Date
Msg-id 718368.1742404967@sss.pgh.pa.us
Whole thread Raw
In response to Re: After upgrading libpq, the same function(PQftype) call returns a different OID  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: After upgrading libpq, the same function(PQftype) call returns a different OID
List pgsql-general
Adrian Klaver <adrian.klaver@aklaver.com> writes:
> On 3/18/25 23:41, Sebastien Flaesch wrote:
>> I was not expecting this file to be in a "server" folder, when it's to 
>> be used for client apps.

> Not surprising. As I understand it this is the code used to build the 
> type entries in the system catalog pg_type.

More the other way around: pg_type_d.h is built from the authoritative
source files pg_type.h and pg_type.dat, according to the process
described here:

https://www.postgresql.org/docs/devel/bki.html

>> And still, I do not trust the content.

Why not?  If it's the "Backwards compatibility" comment that's
bothering you, a look at pg_type.h will show you that that's
only intended to apply to the CASHOID and LSNOID symbols.
Everything below that in pg_type_d.h is machine-generated.

            regards, tom lane



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: size of attributes table is too big
Next
From: Siraj G
Date:
Subject: Re: size of attributes table is too big