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-19 16:53:31
Message-ID: 7a07f957-bb8c-413b-806a-504a5cd12072@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/18/25 23:41, Sebastien Flaesch wrote:
> You are right Adrian, I did not search properly I found the header file
> here:
>
> sf(at)toro:/opt3/dbs/pgs/17.4$ ls -l
> include/postgresql/server/catalog/pg_type_d.h
> -rw-r--r-- 1 sf sf 9672 Mar 13 17:05
> include/postgresql/server/catalog/pg_type_d.h
>
> 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. As was mentioned in your
previous link:

https://www.postgresql.org/docs/17/libpq-exec.html#LIBPQ-PQFTYPE

the suggested way to get type information is:

"You can query the system table pg_type to obtain the names and
properties of the various data types. "

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

Then do as suggested above.

>
> Seb
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Siraj G 2025-03-19 17:06:08 size of attributes table is too big
Previous Message Tom Lane 2025-03-19 16:13:26 Re: Restoring only a subset of schemas