Re: After upgrading libpq, the same function(PQftype) call returns a different OID
От | Adrian Klaver |
---|---|
Тема | Re: After upgrading libpq, the same function(PQftype) call returns a different OID |
Дата | |
Msg-id | 7a07f957-bb8c-413b-806a-504a5cd12072@aklaver.com обсуждение исходный текст |
Ответ на | Re: After upgrading libpq, the same function(PQftype) call returns a different OID (Sebastien Flaesch <sebastien.flaesch@4js.com>) |
Ответы |
Re: After upgrading libpq, the same function(PQftype) call returns a different OID
|
Список | 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@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.klaver@aklaver.com
В списке pgsql-general по дате отправления: