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

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>, "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 15:49:37
Message-ID: CAFCRh-9OdEOCMKpuo+cHkdJkQJXjXxurcVsAp_ia62COiXaSvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Mar 20, 2025 at 4:43 PM Sebastien Flaesch
<sebastien(dot)flaesch(at)4js(dot)com> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2025-03-20 16:03:51 Re: Export operation efficiency in read replica
Previous Message Sebastien Flaesch 2025-03-20 15:42:39 Re: After upgrading libpq, the same function(PQftype) call returns a different OID