From: Tom Lane <tgl@sss.pgh.pa.us>
To: fairyfar@msn.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19429: An issue regarding the processing of Oid as an int type in ecpg
In-reply-to: <19429-aead3b1874be1a99@postgresql.org>
References: <19429-aead3b1874be1a99@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 12 Mar 2026 06:31:58 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2247547.1773615628.1@sss.pgh.pa.us>
Date: Sun, 15 Mar 2026 19:00:28 -0400
Message-ID: <2247548.1773615628@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2247548.1773615628%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Part of the code caches and calculates the Oid as an int type in ecpg.
> We know that Oid is unsigned int. When the Oid value is greater than or
> equal to 2^31, it exceeds the value range of the int type. There are
> potential problems in processing Oid with the int type. For example, when
> formatting Oid with "%d", negative values may occur.

> Through analysis and testing, it is found that the ecpg part of the code has
> not caused any problems so far, but it is running in an obscure way.

Yeah, it does work as-is, but it's relying on undocumented details
about what the server will do with something like "oid=-1".

I reviewed your patch and pushed it.  For future reference, it's not
great to send patches via our bug report form; whitespace gets mangled
and it's quite painful to reconstruct.  Better to just send email to
pgsql-hackers with the patch in an attachment.

			regards, tom lane