Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Sami Imseih <samimseih@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: query_id: jumble names of temp tables for better pg_stat_statement UX
Date: Tue, 25 Mar 2025 19:56:29 -0500
Message-Id: <70BA294B-5A33-4F47-A637-8011C1F279CB@gmail.com>
References: <Z-NLelZdH3GaLRNK@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Christoph Berg <myon@debian.org>,
 Lukas Fittl <lukas@fittl.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 ma lz <ma100@hotmail.com>
In-Reply-To: <Z-NLelZdH3GaLRNK@paquier.xyz>
To: Michael Paquier <michael@paquier.xyz>
Archived-At: <https://www.postgresql.org/message-id/70BA294B-5A33-4F47-A637-8011C1F279CB%40gmail.com>
Precedence: bulk


> If I get the difference right, semantically would apply to concepts
> related to linguistics, but that's not what we have here, so you are
> using a more general term.

FWIW, the pg_stat_statements docs in a few places refer to=20
queries that may look different but have the same meaning=20
as =E2=80=9Csemantically equivalent=E2=80=9D, this is why I used the same=20=

terminology here.  But, I have no issue with the simplified
rewrite either.

The patch LGTM as well.=20

Regards,


Sami Imseih=20
Amazon Web Services (AWS)=