Re: [survey] New "Stable" QueryId based on normalized query text - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: [survey] New "Stable" QueryId based on normalized query text
Date
Msg-id CAOBaU_atk6WMxA=ajNURThwmJ2jMyEfkE88TSkwtOfvk4gXrFA@mail.gmail.com
Whole thread Raw
In response to Re: [survey] New "Stable" QueryId based on normalized query text  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: [survey] New "Stable" QueryId based on normalized query text
List pgsql-hackers
On Wed, Mar 20, 2019 at 10:30 PM legrand legrand
<legrand_legrand@hotmail.com> wrote:
>
> maybe this patch (with a GUC)
> https://www.postgresql.org/message-id/55E51C48.1060102@uptime.jp
> would be enough for thoses actually using a text normalization function.

The rest of thread raise quite a lot of concerns about the semantics,
the cost and the correctness of this patch.  After 5 minutes checking,
it wouldn't suits your need if you use custom functions, custom types,
custom operators (say using intarray extension) or if your tables
don't have columns in the same order in every environment.  And there
are probably other caveats that I didn't see;


pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: [survey] New "Stable" QueryId based on normalized query text
Next
From: legrand legrand
Date:
Subject: Re: [survey] New "Stable" QueryId based on normalized query text