From: Tom Lane <tgl@sss.pgh.pa.us>
To: Julien Rouhaud <rjuju123@gmail.com>
cc: marcus.kempe@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17668: Query normalization generates multiple queryId:s for
 calls to the same procedure
In-reply-to: <20221027160834.uxhmt473grlpfv5x@jrouhaud>
References: <17668-e25abc1f5375b095@postgresql.org>
 <20221027160834.uxhmt473grlpfv5x@jrouhaud>
Comments: In-reply-to Julien Rouhaud <rjuju123@gmail.com>
	message dated "Fri, 28 Oct 2022 00:08:34 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <748391.1666895297.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 27 Oct 2022 14:28:17 -0400
Message-ID: <748392.1666895297@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/748392.1666895297%40sss.pgh.pa.us>
Precedence: bulk

Julien Rouhaud <rjuju123@gmail.com> writes:
> On Thu, Oct 27, 2022 at 01:49:18PM +0000, PG Bug reporting form wrote:
>> I would have expected both calls to be normalized and fingerprinted to =
one
>> and the same queryId.

> Agreed, and that's actually a known problem that is currently being work=
ed on.
> You can look at
> https://www.postgresql.org/message-id/flat/36e5bffe-e989-194f-85c8-06e7b=
c88e6f7%40amazon.com
> for details about the discussion and in-progress fix.

Um ... that seems unrelated.  AFAICS the OP is complaining about
the fact that '42'::int4::int8 is not identical to '42'::int8.
Well, they're not.  I seriously doubt that we would or should
consider trying to get queryjumble to mask that.

			regards, tom lane