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

From Luca Ferrari
Subject Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Date
Msg-id CAKoxK+5dRwuE-BH7S6HfzNm6W8CFL3ZGgJ39+BTsH3b=DJ0dfQ@mail.gmail.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>)
List pgsql-general
On Thu, Mar 20, 2025 at 8:18 AM Sebastien Flaesch
<sebastien.flaesch@4js.com> wrote:
>
> Let's not deviate from my request:
>
> I have implemented various DB client modules using the C client APIs, for Oracle DB, SQL Server, IBM DB2,
MySQL/MariaDB,SQLite and PostgreSQL. 
>

Good for you!
I don't think anybody is trying to deviate from your request, the
point is as described in the documentation of PQftype you have been
already pointed out. And according to me, the approach is flexible
enough to allow for extending the type system without problems.
Last, it is not clear to me what the original problem (getting a
different oid from your libpq example) was generated from: did you
queried the catalog?

Luca



pgsql-general by date:

Previous
From: Sebastien Flaesch
Date:
Subject: Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Next
From: Paul Allen
Date:
Subject: Bloated toast table with empty associated table