| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(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-20 10:47:37 |
| Message-ID: | CAKoxK+5dRwuE-BH7S6HfzNm6W8CFL3ZGgJ39+BTsH3b=DJ0dfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 20, 2025 at 8:18 AM Sebastien Flaesch
<sebastien(dot)flaesch(at)4js(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Allen | 2025-03-20 11:39:39 | Bloated toast table with empty associated table |
| Previous Message | Sebastien Flaesch | 2025-03-20 07:17:47 | Re: After upgrading libpq, the same function(PQftype) call returns a different OID |