From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: After upgrading libpq, the same function(PQftype) call returns a different OID |
Date: | 2025-03-19 17:22:47 |
Message-ID: | 718368.1742404967@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Siraj G | 2025-03-19 17:32:04 | Re: size of attributes table is too big |
Previous Message | Adrian Klaver | 2025-03-19 17:17:10 | Re: size of attributes table is too big |