Re: After upgrading libpq, the same function(PQftype) call returns a different OID

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>
Cc: "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-18 18:41:39
Message-ID: 295e06b4-ff5d-4d82-ba56-1bab24be6bbc@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2025-03-18 23:18:03 Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Previous Message Christoph Berg 2025-03-18 16:51:54 query_id: jumble names of temp tables for better pg_stat_statement UX