From: M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
To: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: After upgrading libpq, the same function(PQftype) call returns a
 different OID
Thread-Topic: After upgrading libpq, the same function(PQftype) call returns a
 different OID
Thread-Index: AduV23zLkRPb77LLTluClfIN9ptbAw==
Date: Sat, 15 Mar 2025 18:53:08 +0000
Message-ID:
 <PAWPR07MB1009569596278D85AC691BBF4AEDD2@PAWPR07MB10095.eurprd07.prod.outlook.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0:
 =?us-ascii?Q?xLZxOuBNpoAukF4zj/9Xwy8mrbOWpj135Ssm1l4hwr+3tIPCjB/JWtBNYZc/?=
 =?us-ascii?Q?40d8PpFZpZ/MLaT4SW2ZHq5vT7pY+smRYQCj5jioKg1YjBejqbEW+40uzdlm?=
 =?us-ascii?Q?uqJ7oOot+GHOGemp1eq8K64kDqq+JbvaF/CedyOQMv8wL0wTIRzJUvhMEbAG?=
 =?us-ascii?Q?F82kzIOLF5ySBZtMEUVDrDdhpochG5wWKQGMa2hRyJepT2XtFORmGBH6rktK?=
 =?us-ascii?Q?B9AgwZZoj7WhHS+siQoSUSXeIoWo1vAXYx+nkm3ZWEPYnhqJX7B4tcC6R7BO?=
 =?us-ascii?Q?hgwLgySSN6J1GTGAKmhQ3/wDFaDDmkY912ReWysWEqCE1TJU/8ZizRPy11/B?=
 =?us-ascii?Q?e44ZcdoF3FdFhcViH0rHHr/gcDz1zgKcWXcmr2Ht4X+jBRE10GIvmCCGBRt+?=
 =?us-ascii?Q?dC6k/VAvHNgOXPJfarBlL/jjd3bJl/8crbN6eTA5ESSD1PZyWbGeg8+KQK0k?=
 =?us-ascii?Q?Fjt5nV/GNhiY30Gb3wx5ZAb4wjS+ZBqIC7beVq7vbswLK0wSaJA1/FzTL0Dm?=
 =?us-ascii?Q?KV6EI0717eW53pMnUVh+IckDvxQ9n8U1QspnMwHYAfSxFApR0x0+B95bbwKT?=
 =?us-ascii?Q?ZVzVS+eiy99+Ujch1SiIvFdGrpegQDT1Vra4XzJWKBRBuq1tf75O6HcGUjeN?=
 =?us-ascii?Q?GblCGeOhiGzmUzypoV+vRuHUJf8ww/CLoPRptInl75Cdu0re2W+Km4B5qD1H?=
 =?us-ascii?Q?1b5aHxoNXzwcZyBzMKc1PRxwve8xCwMyvjUcT76aJaFnYNXP+oCH2e2A0Jaa?=
 =?us-ascii?Q?+X0aUPgWbuVYJdy9tr295bd1xH+sRAN5yWDyYw2j/04/lfc2oqueZhxv/lEr?=
 =?us-ascii?Q?lWf3OQETZs9mT8oWemrnnghguQTqWsHdLz84j9U0HjEavlT24YSKo0xwHr6C?=
 =?us-ascii?Q?Fmp4WEm0NxNJ6aG93cZmm80zmzzhXY3QnJPXKsSeb/bqioYVUSgWHFjEtmOz?=
 =?us-ascii?Q?4XOzj1V8Dqz3t0EMdQjmHLAsaoPMnzDobLYmV2kzCRMDDuub0ZkDIXCBOfPh?=
 =?us-ascii?Q?5rFSX2lDKrMnobErg1RpMx0xpf2JpNC3+MQOcjE4L/EN6pYQhGduVW5008mT?=
 =?us-ascii?Q?zMtkf+/mQ0b/lA1WP1MyVc4LopXQuyTLuC5e/ayGzW0JDxJVLZJRWeVuacXF?=
 =?us-ascii?Q?XE4Zp3L/42a8R/XbeAP50FiUnVR80yNEdeimM8c4V+SrsKNDye7xq5NeCBFw?=
 =?us-ascii?Q?U9VLwKHiB+Zc9FvCYDZrFKwhyjxrPApM/5bkDBPqkS4vqPY/dCT1bFRzty0n?=
 =?us-ascii?Q?pAwZuiEsDokq2UNLoPEPwrJBN4RIvbtaziKjFxbSuBk+hUCi9vBPkSyQ+T03?=
 =?us-ascii?Q?Q2IVw0ycM5jWyB8+Pa6n1+US5fPiWpzxQZIhVyIiPZ2zNBe1IPSToQj+bdJb?=
 =?us-ascii?Q?nF1bkCR9/aGOCWbFCgubuYwipSxxQGIb0BZZEBFEU+fZciuxiz/1nkOwZzUr?=
 =?us-ascii?Q?c8POdC/GxQp8+Ab76shnvGx0qVSqHyUp36Rgg21q2euhsfmqM4nwswEgKU0R?=
 =?us-ascii?Q?2Fe1b+TXwXC83hI5N1S2nsuoBt/OdZkY5Gt+iiRO0JkgStOLYb8lRqK8LTne?=
 =?us-ascii?Q?lVke56z4XV4taMFhJK55FGlj90T9xDzjiVVzKbD3FST7m/7YeGavmUW9gRMt?=
 =?us-ascii?Q?cg=3D=3D?=
Content-Type: multipart/alternative;
	boundary="_000_PAWPR07MB1009569596278D85AC691BBF4AEDD2PAWPR07MB10095eu_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PAWPR07MB10095.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7f393496-7f5e-4762-78d5-08dd63f2a069
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2025 18:53:08.0791
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4g53IkmdHjvJgMe2jS15bNAdMfxRcfDx2IgI4Jf8ltyrjL4VJMRW/r85Lvl2JybsJmaV++InPOL/E98NvthgOWJvv7YK86kuj8kdyK4xep4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PAXPR07MB7935
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/PAWPR07MB1009569596278D85AC691BBF4AEDD2%40PAWPR07MB10095.eurprd07.prod.outlook.com>
Precedence: bulk

--_000_PAWPR07MB1009569596278D85AC691BBF4AEDD2PAWPR07MB10095eu_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

We are using PostgreSQL libpq in our application. The code worked fine for =
the past four years, but after upgrading the library, the function PQftype =
is returning unexpected values for some columns.
Specifically, the issue occurs with a column of type timestamp(3) without t=
ime zone.

What could be causing this change, and how can we resolve it?"

Postgres Version(upgraded from 11.18 to 13.20)

Example:

Before the libpq Upgrade (Expected Behavior)

Let's say your PostgreSQL database has a table:

CREATE TABLE example (
    id SERIAL PRIMARY KEY,
    filetime TIMESTAMP(3) WITHOUT TIME ZONE
);

In the old version of libpq, calling PQftype on the filetime column returns=
:

Oid filetime_oid =3D PQftype(res, 1); // Assuming 'filetime' is at index 1
printf("Filetime column OID: %u\n", filetime_oid);

Expected output (before upgrade):
Filetime column OID: 1114

After the libpq Upgrade (Unexpected Behavior)
After upgrading libpq, the same function call returns a different OID, such=
 as 123456.

What could be the reason?

Regards
Tarkeshwar


--_000_PAWPR07MB1009569596278D85AC691BBF4AEDD2PAWPR07MB10095eu_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	font-size:11.0pt;
	font-family:"Aptos",sans-serif;
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Aptos",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:11.0pt;
	mso-ligatures:none;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-IN" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We are using <b>PostgreSQL libpq</b> in our applicat=
ion. The code worked fine for the past four years, but after upgrading the =
library, the function
<b>PQftype</b> is returning unexpected values for some columns. <o:p></o:p>=
</p>
<p class=3D"MsoNormal">Specifically, the issue occurs with a column of type=
 <b>timestamp(3) without time zone</b>.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">What could be causing this change, and how can we re=
solve it?&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"5" cellpadding=
=3D"0">
<tbody>
<tr>
<td colspan=3D"2" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal">Postgres Version(upgraded from 11.18 to 13.20) <o:p>=
</o:p></p>
</td>
</tr>
<tr>
<td colspan=3D"2" style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:18.0pt;color:red">Exa=
mple</span></u></b><span style=3D"font-size:18.0pt;color:red">:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Before the libpq Upgrade (Expected Behavior)<o:p>=
</o:p></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Let's say your PostgreSQL database has a table:<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">CREATE TABLE example (<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp; id SERIAL PRIMARY KEY,<o:p></o:p>=
</p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp; filetime TIMESTAMP(3) WITHOUT TIM=
E ZONE<o:p></o:p></p>
<p class=3D"MsoNormal">);<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In the old version of <b>libpq</b>, calling PQftype =
on the filetime column returns:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Oid filetime_oid =3D PQftype(res, 1); // Assuming 'f=
iletime' is at index 1<o:p></o:p></p>
<p class=3D"MsoNormal">printf(&quot;Filetime column OID: %u\n&quot;, fileti=
me_oid);<o:p></o:p></p>
<p class=3D"MsoNormal"><b><o:p>&nbsp;</o:p></b></p>
<p class=3D"MsoNormal"><b>Expected output (before upgrade):</b><o:p></o:p><=
/p>
<p class=3D"MsoNormal">Filetime column OID: 1114<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</td>
</tr>
<tr style=3D"height:10.5pt">
<td colspan=3D"2" style=3D"padding:.75pt .75pt .75pt .75pt;height:10.5pt">
<p class=3D"MsoNormal"><b>After the libpq Upgrade (Unexpected Behavior)<o:p=
></o:p></b></p>
<p class=3D"MsoNormal">After upgrading <b>libpq</b>, the same function call=
 returns a different OID, such as 123456.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:red">What could be the reason? =
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</td>
</tr>
<tr>
<td style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal">Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Tarkeshwar<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</body>
</html>

--_000_PAWPR07MB1009569596278D85AC691BBF4AEDD2PAWPR07MB10095eu_--