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

From Adrian Klaver
Subject Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Date
Msg-id 295e06b4-ff5d-4d82-ba56-1bab24be6bbc@aklaver.com
Whole thread Raw
In response to Re: After upgrading libpq, the same function(PQftype) call returns a different OID  (Sebastien Flaesch <sebastien.flaesch@4js.com>)
Responses Re: After upgrading libpq, the same function(PQftype) call returns a different OID
List pgsql-general
On 3/16/25 02:30, Sebastien Flaesch wrote:
> 
> Hello,
> 
> I think the column type identification with PQftype() needs some 
> review/clarification.
> 
> It's a pity that libpq does not have an API to return directly the 
> actual type name of a column.
> 
> The doc 
> <https://www.postgresql.org/docs/17/libpq-exec.html#LIBPQ-PQFTYPE> says:
> 
> You can query the system table |pg_type| to obtain the names and 
> properties of the various data types. *The OIDs of the built-in data 
> types are defined in the file |catalog/pg_type_d.h| in the 
> PostgreSQL installation's |include| directory.*
> 
> After building PostgreSQL *17.4* from the sources, I cannot find this 
> pg_type_d.h header file in the installation directory. Maybe I am 
> missing some configure option?

Went I built from source in ended up in:

/usr/local/pgsql/include/server/catalog/


-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Evgeniy Ratkov
Date:
Subject: Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
Next
From: Andrus
Date:
Subject: How to convert wal log to sql commands starting from specified time