Re: BUG #17668: Query normalization generates multiple queryId:s for calls to the same procedure - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17668: Query normalization generates multiple queryId:s for calls to the same procedure
Date
Msg-id 748392.1666895297@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17668: Query normalization generates multiple queryId:s for calls to the same procedure  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: BUG #17668: Query normalization generates multiple queryId:s for calls to the same procedure
Re: BUG #17668: Query normalization generates multiple queryId:s for calls to the same procedure
List pgsql-bugs
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 worked on.
> You can look at
> https://www.postgresql.org/message-id/flat/36e5bffe-e989-194f-85c8-06e7bc88e6f7%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



pgsql-bugs by date:

Previous
From: Παναγιώτης Ρουσάλης
Date:
Subject: PostrgreSQL 15 installation
Next
From: PG Bug reporting form
Date:
Subject: BUG #17669: Invalid TOAST pointer in PL/pgSQL variable