Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: After upgrading libpq, the same function(PQftype) call returns a different OID
From: Dominique Devienne <ddevienne@xxxxxxxxx>
Date: Thu, 20 Mar 2025 16:49:37 +0100
Cc: Tom Lane <tgl@xxxxxxxxxxxxx>, Adrian Klaver <adrian.klaver@xxxxxxxxxxx>, M Tarkeshwar Rao <m.tarkeshwar.rao@xxxxxxxxxxxx>, "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <DBAP191MB12895511C8AF01672076F8E3B0D82@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM>
References: <PAWPR07MB1009569596278D85AC691BBF4AEDD2@PAWPR07MB10095.eurprd07.prod.outlook.com> <3498256.1742065328@sss.pgh.pa.us> <DBAP191MB1289124F5D8690DF3F72F62CB0DC2@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM> <295e06b4-ff5d-4d82-ba56-1bab24be6bbc@aklaver.com> <DBAP191MB1289C92E15014C2627C49BEBB0D92@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM> <7a07f957-bb8c-413b-806a-504a5cd12072@aklaver.com> <718368.1742404967@sss.pgh.pa.us> <DBAP191MB1289417EA192457D9663350EB0D82@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM> <983724.1742481099@sss.pgh.pa.us> <DBAP191MB12895511C8AF01672076F8E3B0D82@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM>

On Thu, Mar 20, 2025 at 4:43 PM Sebastien Flaesch
<sebastien.flaesch@xxxxxxx> wrote:
> OR.... ( I guess I start to understand the code... ) it this comment only for:
> #define CASHOID MONEYOID
> #define LSNOID  PG_LSNOID

That's what Tom already replied, yes. --DD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Sebastien Flaesch

References:
- After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: M Tarkeshwar Rao
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Tom Lane
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Sebastien Flaesch
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Adrian Klaver
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Sebastien Flaesch
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Adrian Klaver
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Tom Lane
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Sebastien Flaesch
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Tom Lane
- Re: After upgrading libpq, the same function(PQftype) call returns a different OID
  - From: Sebastien Flaesch

Prev by Date: Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Next by Date: Re: Export operation efficiency in read replica
Previous by thread: Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Next by thread: Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]