Re: queryId constant squashing does not support prepared statements

On 2025-May-02, Michael Paquier wrote:

> That depends.  If we conclude that tracking this information through
> the parser based on the start and end positions in a query string
> for a set of values is more relevant, then we would be redesigning the
> facility from the ground, so the old approach would not be really
> relevant..

I disagree that a revert is warranted for this reason.  If you want to
change the implementation later, that's fine, as long as the user
interface doesn't change.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"Doing what he did amounts to sticking his fingers under the hood of the
implementation; if he gets his fingers burnt, it's his problem."  (Tom Lane)